patternModerate
What Key Performance Indicators (KPIs) are used to measure DevOps?
Viewed 0 times
whatareusedkpisindicatorsperformancemeasuredevopskey
Problem
I am trying to drive good behaviors within a DevOps transformation programme, to support this I am looking at identifying actionable metrics around the operations disciplines:
To be absolutely clear, these are functions that used to belong to the operations organization and are now owned by the Agile/DevOps organization. There are existing KPIs that drive bad behaviors are:
What Key Performance Indicators can be used to encourage good behaviour in a DevOps Programme?
- Problem and Incident Management
- Capacity Management
- Change and Release Management
To be absolutely clear, these are functions that used to belong to the operations organization and are now owned by the Agile/DevOps organization. There are existing KPIs that drive bad behaviors are:
- Time to Root Cause Analysis completed:
- Drives incomplete RCAs just to get them into the system on time.
- Test execution duration:
- Disables long running tests, regardless of their business value.
- Average utilization of cloud services:
- Encourages over-commitment of compute resources, resulting in slow response times
What Key Performance Indicators can be used to encourage good behaviour in a DevOps Programme?
Solution
I don't think there are any "universal" DevOps KPIs. For example, velocity is great, unless it's not a key driver for your business. Amazon cares a lot about velocity because they have a massive retail operation. That's less important for a small app with 100 users.
This begs the question: how do you select the best KPIs relevant to your business? That's a research and discovery process that involves your entire Enterprise.
What do you care about?
What keeps your business stakeholders up at night? What determines whether you make money this quarter or not? The list above might include some of those things, or it might not. Make your list, then figure out how to align incentives across every department to achieve them.
Incentives drive behavior, so decide collaboratively on SMART goals. Pick two or three items off your brainstormed list, and start a measure/fix feedback cycle for each. Don't pick too many at once- you're more likely to succeed by focusing hard on two or three things.
This begs the question: how do you select the best KPIs relevant to your business? That's a research and discovery process that involves your entire Enterprise.
What do you care about?
- Quality
- Reliability
- Maintainability
- Velocity
- Process Improvement
- Service Levels
What keeps your business stakeholders up at night? What determines whether you make money this quarter or not? The list above might include some of those things, or it might not. Make your list, then figure out how to align incentives across every department to achieve them.
Incentives drive behavior, so decide collaboratively on SMART goals. Pick two or three items off your brainstormed list, and start a measure/fix feedback cycle for each. Don't pick too many at once- you're more likely to succeed by focusing hard on two or three things.
Context
StackExchange DevOps Q#738, answer score: 12
Revisions (0)
No revisions yet.