At the Velocity conference in 2009 John Allspaw and Paul Hammond gave a talk called “10 deploys per day”._ During that talk they coined the term DevOps. They changed the world.
Traditionally, Development and Operations teams have conflicting goals. Operations want to keep services and systems running as safe and stable as possible. Development, on the other hand, wants to push features to production as fast as possible. We end up with a conflict because Ops loathe change, while Dev are constant agents of change.
What the people in each silo tend to forget is that they are both on the same mission: to enable business. DevOps is about finding the tools and creating the culture that allows Dev and Ops to work together in the most harmonious way. It’s about making sure that all the relevant parts of an organization work together to produce business value quickly, safely and sustainably.
Some people have started using terms like DevTestOps and DevSecOps to make sure all stakeholders are heard. But, whatever terminology we decide to use, the core DevOps values remain the same: collaboration, communication, transparency, and a shared commitment to continuously improve the way we deliver quality and value.
Organizations that don’t practice DevOps experience many of the same problems. Typically, Developers have to wait to get the computational resources they need while the Operations team has to deal with applications that haven’t been thoroughly tested in a production-like environment. This wastes valuable time and creates huge frustrations in both teams.
DevOps is about having our teams understand each other’s needs and frustrations. It’s about having developers understand how their application will be run and having Operations staff enable development at speed. DevOps practices yield fast feedback, safe releases, and full transparency across the organization.
To practice DevOps successfully requires the whole organisation to commit to a single culture of collaboration. It requires commitment and implementation strategies from management level to junior developers. Whatever your business domain or DevOps maturity level, Praqma would love to help you.
Some of the thought leaders in the DevOps movement collect data from software organizations at all levels of DevOps maturity to produce an annual “State of DevOps” report.
It gives us solid evidence showing that organizations practicing DevOps perform far better than those who aren’t. In fact, DevOps teams are more than twice as likely to achieve or exceed their objectives, like operating efficiency and customer satisfaction. They are also able to recover from failures almost 100 times faster and they are 440 times faster from commit to deployment. DevOps not only makes us faster, it makes us safer too.
If you are curious about the state of DevOps in your organization and how to move forward, consider a Continuous Delivery Assessment. We will help you analyze your level of maturity, and build a roadmap with tangible tasks to improve yourself. Do it!
We help customers in Denmark, Sweden and Norway, and have offices in Copenhagen, Aarhus, Oslo, Malmö, Stockholm and Gothenburg.