From Agile to DevOps
“We did it!” Says the CEO of a large multinational in his weekly board meeting.
“It’s been a major transformation that took over a year to achieve, but we finally made it. All of our teams are Agile and use Scrum to develop their software.”
He walks up to his CTO and continues: “Could you tell me what the key results are in terms of software delivery speed and quality?” The CTO stands up and proudly tells the rest of the board that all of his teams are developing new features twice as fast and the number of bugs decreased with over 50%.
But then, the lead developer interrupts him: “I agree, these are all great achievements, but all of our competitors are already beyond Agile. They are generating new software twice as fast whilst ensuring the same level of quality.”
The CEO quickly asks how they are able to do this. Is it because they have better developers or more teams?
“No” says the developer, “It’s because their developers work closely together with Operations with a practice called DevOps.”
DevOps is the practice of creating multidisciplinary teams that consist of development engineers (Dev) and operations (Ops), working together in the entire development- and service lifecycle, from design through the development process to production support. In order to achieve this, the traditional separation between development and operations needs to be broken. This is because both areas of expertise are required to successfully deliver and maintain software which meets the functional and non-functional requirements.
Agile vs DevOps
Agile vs DevOps. They both serve a common goal: “Deliver value to customers fast and often”
But there is a difference.
If we look at Agile methodologies in the IT landscape, like Scrum and Kanban, they focus on the development of software. For example slicing requirements, working in smaller teams, producing “potentially shippable code” in shorter iterations.
DevOps, on the other hand, is focused on development and operations. It focuses on reliable, repeatable and the safest way of deployments and keeping the product up and running. Agile is often seen as an enabler of DevOps because of its focus on working software and effective communication and collaboration practices.
Why you need DevOps in your life
Ok, so DevOps breaks down the silo’s called Dev and Ops. But why would you want to do that? What are the benefits? After all, you’re already Agile, right?
Increase your software delivery speed so you can innovate for customers faster, adapt to changing markets better, and grow more efficient at driving business results. DevOps enables your developers and operations teams to achieve these results and reduce the time-to-market.
Continuous software delivery
Secondly, a continuous flow of software delivery. Increase the frequency and pace of releases so you can innovate and improve your product faster. The quicker you can release new features and fix bugs, the faster you can respond to your customers’ needs and build competitive advantage.
DevOps helps to improve the communication and collaboration between the developers and operations. Testers get involved earlier in the development process which helps to improve the quality of the product because they are able to detect bugs earlier. But this also helps to eliminate waste by removing unnecessary hand-overs between Dev and Ops.
Where Agile provides you with a process in which value is defined and created, DevOps ensures that the organization is able to redeem this value.
In short, DevOps helps you reduce your time-to-market, increase the software quality and improve the collaboration by breaking down the silo’s between Dev and Ops in a way Agile never could.
That is why you need DevOps in your organization!
Do you want to know more about DevOps? Take a look at our DevOps Foundation training!
For more information about the DevOps Foundation training, check out this blog: Getting the foundation right!