6 Great DevOps Metrics — and How to Choose the Right Metrics

Learn what makes a good DevOps metric, and discover six metrics most organizations can use to evaluate the performance of DevOps teams.

What are DevOps Metrics?

Characteristics of Useful DevOps Metrics

  • Measurable-metrics must have standardized values that are consistent over time.
  • Relevant-metrics should measure aspects that are important to the business.
  • Reliable-team members cannot affect or “game” the measurement.
  • Actionable-long-term analysis of the metric should provide insights into possible improvements in systems, workflows, strategies, etc.
  • Traceable-the metrics should point directly to a root cause, not just allude to a general problem.
  • Based on non-DevOps values-for example, metrics that measure adherence to requirements are more suited for a waterfall development environment.
  • Based on competition-if the best performers are the “winners” and everyone else “loses”, it is difficult to expect communication and collaboration within and between teams. Don’t build metrics based on competition between team members or between teams (e.g. number of failed builds or fatal errors). Teams will become obsessed with improving the metric, rather than discovering real problems and working together to resolve them.
  • Vanity metrics-metrics must support teamwork. Vanity metrics indicate some capability, but are not really indicative of business effectiveness. For example, the number of lines of code written each week is irrelevant because code can disappear completely during refactoring, and sometimes less code is better for the organization. The number of builds per day doesn’t matter, unless each build really adds value to the end user experience.

6 Key DevOps Metrics

1. Lead Time

2. Deployment Frequency

3. Change Failure Rate

4. Mean Time to Recovery (MTTR)

5. Customer Ticket Volume

6. Defect Escape Rate

Conclusion

  • Lead time-the time needed to push new changes to production
  • Deployment frequency-how often builds are deployed to an environment
  • Change failure rate-how many changes result in defects
  • MTTR-time required to recover from failure
  • Customer tickets-how many problems are filed by customers as support tickets
  • Defect escape rate-how many quality issues make their way to production

--

--

We help tech communities to grow worldwide, providing top-notch tools and unparalleled networking opportunities.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Codemotion

We help tech communities to grow worldwide, providing top-notch tools and unparalleled networking opportunities.