DevOps
When we are asked what DevOps is or how we define it, we don't say well it's a combination or collaboration of or between Developers (Dev) and Operations (Ops) – as much as this is historically true. But DevOps is much more than that.
When we are asked what DevOps is or how we define it, we don't say well it's a combination or collaboration of or between Developers (Dev) and Operations (Ops) – as much as this is historically true. But DevOps is much more than that.
DevOps is a mindset, a culture and a set of technical practices. It provides communication, integration, automation and close cooperation among all the people needed to plan, develop, test, deploy, release and maintain a solution.
DevOps is a recipe that relies on ingredients from three major categories: people, process and automation. Most of the ingredients can be adapted from other well-known practices and sources such as lean, agile, SRE, CI/CD, ITIL, leadership, culture and tools. The secret behind DevOps is how these ingredients are blended and in the right proportions (like any good recipe) in order to increase flow and value to the customer.
There are many different perspectives of what DevOps really is.
Some see DevOps only as something that comes later, after the software has been developed, for rollout or for maintenance. Others assume that single activities or technologies (like CI/CD, pipelines, automation, etc.) and DevOps are synonyms. Whereas many see it for what it really is: a culture, a mindset that, when done right, is integrated and incorporated in every aspect of an organization.