DevOps Metrics in 2019
Effectively competing in today’s digital economy requires companies to have continuous integration, continuous deployment and deliver at the speed required by the business. Fast beats slow. For development groups, the amount of new innovation being implemented and delivered is what helps drive company value.
The technology leaders that have identified the need for change, determined the next steps for changing the development methodology and understand the benefits to the business are challenged to convince C-level executives.
At Compuware we use zAdviser to measure velocity, efficiency and quality. Understanding how fast changes can be delivered, determining the right changes to implement and delivering quality changes will help drive growth within the business.
What are the key benefits to implementing Agile and DevOps? The answer is delivering more updates and new technology faster, at the speed required by the business and with the quality expected by end-users. Velocity, efficiency and quality are the key metrics to know if the change is successful.
If you are in an organization using the waterfall development methodology, then you need to show the future value of change.
The amount of development capacity dedicated to innovation is a key indicator. The more time developers spend delivering new innovation to the business, the more likely the business will drive more revenue and increase customer satisfaction.
The graphs below are the actual innovation charts for two years at Compuware. The first graph shows the metrics for 2013 with Waterfall and the second is 2018 with Agile and DevOps. The overall innovation time in 2013 was 49.1 percent with the lowest week showing 11.5 percent innovation. In contrast, in 2018 overall innovation time was 88.7 percent with a one week low of 69.4 percent.
What About Quality?
The number of defects reported by end-user customers is lower for products supported in both years. The average time to deliver a fix for a reported issue has gone from 122 days to 22 days.
Going from once-a-year to quarterly releases of updates to our technology is a key contributor to the reduction in MTTR (mean time to repair), which directly impacts customer satisfaction and drives company revenue.
Any CIO, CEO or CFO that looks at these graphs would clearly see that there can be benefits from changing the development methodology. In 2013, they would be asking, “What are 88 percent of your developers doing during that lowest week? If there is 49.1 percent innovation, what is the majority (50.9 percent) of our development time delivering?” In Waterfall, the time spent creating detailed designs for features never delivered, release definition documents rarely used and time waiting for testers to provide feedback are a few of the answers.
At Compuware we have been able to increase our innovation, reduce our defects and lower our MTTR. We’ve done this by:
- Implementing DevOps: Integrating all aspects of the development process, including testing, into the agile scrum teams
- Implementing Agile: Working in two-week sprints, releasing to end-user customers quarterly and integrating customer feedback into our development process
- Automated testing: Increasing automated testing and continue to grow code coverage sprint after sprint
- Automation: Having laser focus on automating any manual process to allow developers to focus on innovating
- Implementing a modern DevOps toolchain across the enterprise: Using the same tools across the enterprise allows for consistent measurement, simplified deployment and more productive collaboration
If you are considering a DevOps transformation, don’t know where to start or are in the midst of a transformation, accurate metrics can show progress, identify opportunities or show a starting point. Compuware zAdviser can provide the KPIs for quality, efficiency and velocity. DevOps metrics will provide the necessary information to earn support, maintain traction and help drive business value.
This post originally appeared on LinkedIn.