Before you start hammering this post with comments, what I mean by the title is that DevOps has evolved so much over the last few years that the term 'DevOps' simply doesn't make sense anymore. What it signifies is no longer related to just Developers and Operations teams. It applies to multiple teams across an organization. The principles and methodologies however, still hold and continue to evolve.
From what we all come across when we talk to our clients, and in general, the perception of DevOps is that it is some sort of methodology purely related to Developers and Operations.
That sounds true based on how it is coined. However, it is not.
Every movement or methodology starts out from within a particular community. DevOps is no different. It started out from within the Developer and Operations community to address the never ending issues around communication, collaboration and integration between these teams. The aspiration being to deliver services and features to the customer when they (may) want it rather than only when the teams can deliver. If you have worked in any scale of enterprise/business - small, medium, large - you would know exactly what I am referring to here.
The end goal of DevOps is to enhance customer delight and increase revenue.
This can be accomplished by delivering new features to customers at a rapid pace, and at the time they (may) want it. For this to happen, agility among Dev and Ops teams is often not sufficient. Based on the type and scale of an enterprise/business, there are usually many other teams involved in successfully launching a feature/service/product, including: leadership, marketing, sales, product owners, developers, operations, security teams, network architecture teams, architecture review committees, customer support, legal, and finance. Without a methodology that brings together all the relevant teams as and when needed, it is highly unlikely that a business can continuously deliver at high velocity. DevOps has evolved in the past few years to encompass and facilitate better communication and culture among all these teams.
The DevOps tools have evolved; culture & change management has evolved.
DevOps is not a technology or culture, it is an organic body of practices based on technology tools, cultural change and continuous improvement. It's "organic" because the principles continuously evolve over time. However, there is no definitive body responsible for defining a specification or framework. Hence, there are many definitions available out there. Based on how it evolved over the past few years, talking to various DevOps practitioners, and from my own personal experience and school of thought, I agree with Chef's Chief Product Officer - Adam Jacobs' definition of DevOps:
A cultural and professional movement, focused on how we build and operate high velocity organizations, born from the experiences of its practitioners.
Note that he doesn't mention Developers or Operations; the definition applies to practitioners who are focused on delivering features and services rapidly to the customers in high velocity organizations.
The point I hope to drive across in this post is that, put simply: DevOps principles and methodologies are not just related to Developers and Operations teams. I've also touched on enabling a concept/process we call "business@velocity", but I will talk more about that in a separate post. So stay tuned!