DevOps: What does success look like?
The DevOps transformation journey is generally not linear and maturity levels don't have perfectly-defined boundaries. An organization can be considered mature in one phase of the DevOps lifecycle while appearing immature at other levels.
IMPORTANT: Avoid comparing the results of one team’s metrics with a different team. Measure the improvement of each team against their own baseline.
DevOps is often equated with engineering excellence, and as such, there is a desire and drive for continuous improvement. Organizations that are successful with their DevOps transformation follow a strategy of assessing their current state, identifying the primary pain points, and then working to address the areas highlighted for improvement. Success can best be measured by advances in the software delivery pipeline's measurable aspects and improved development team satisfaction. Based on our experience, these are the key metrics to track for DevOps maturity:
- Deployment frequency - High-maturity organizations have deployments occur on-demand, multiple times per day.
- Lead time for changes - Organizations with high DevOps maturity will see lead times (when a developer begins work to when the code is deployed to production) between one day and one week at most.
- Time to restore service - When a service fails, the time to restore service for high-performing DevOps teams is less than one day.
- Change failure rate - The percentage of changes deployed to production that cause a service impairment or outage is less than 15% for mature DevOps teams.
As long as each team consistently improves toward their specific goals, we consider them successful in their DevOps journey. Each team will face challenges that can slow down or possibly stop improvement.
Why DevOps?
Previous step:
Next step:
DevOps: The challengesWas this content helpful?
Connect, share, or get additional help
Atlassian Community