Home / IT Metrics / Are You Measuring What Matters with DevOps Metrics?

Are You Measuring What Matters with DevOps Metrics?

The newer the business discipline, the more likely that the metrics supporting it are going to be spotty and half-baked. It is just part of the learning process, and several organizations are going through this with DevOps right now. In an article for the Enterprisers Project, Gordon Haff pinpoints some tips for rooting out more effective DevOps metrics.

No Half-Measures

He begins by sharing four important things to remember about DevOps metrics:

  1. There shouldn’t be too many of them.
  2. DevOps metrics should reflect what is important to you.
  3. DevOps metrics should be tied to business outcomes in some manner.
  4. Seek a traceable path to root causes.

Haff says to aim for 10 metrics at most, but they should in tandem project a wide view of operations and of process health. These metrics should ultimately reflect whatever goal or value it is that the business had in mind with DevOps in the first place. It should be clear, one way or another, how they connect back to business outcomes.

And about seeking paths to root causes, Haff says this:

It’s easy to come up with relevant business metrics. They’re the ones that you talk about on your earnings calls. But from the perspective of DevOps and cloud-native infrastructure metrics, there needs to be a traceable path to root causes that operations and development teams can affect. Choosing appropriate metrics are therefore something of a balancing act between being high level enough to have a more or less direct impact on business results while being sufficiently within IT’s purview that they can take direct actions to improve results.

He continues to highlight customer ticket volume, percentage of failed deployments, and job satisfaction respectively as three good examples of DevOps metrics: Customer ticket volume is a reflection of customer satisfaction. Percentage of failed deployments can be used to work out where problems are occurring in your development processes. And the value of job satisfaction as a metric kind of speaks for itself.

For additional thoughts, you can view the original article here: https://enterprisersproject.com/article/2017/7/devops-metrics-are-you-measuring-what-matters

About John Friscia

John Friscia is the Editor of Computer Aid’s Accelerating IT Success. He began working for Computer Aid, Inc. in 2013 and continues to provide graphic design support for AITS. He graduated summa cum laude from Shippensburg University with a B.A. in English.

Check Also

Six IT Design Rules for Digital Transformation

The honeymoon phase of digital transformation is over. Businesses with entrenched systems are realizing that …

Leave a Reply

Your email address will not be published. Required fields are marked *