Four of the key performance indicators (KPI) are mentioned on the DevOps Practices and the DevOps Getting Started poster, under step 5 - VALUE.

devops-mindset-essentials-gdbc-getting-started | Source DevOps-mindset-essentials.

Now that I have this new blog, I can move over this recent article from LinkedIn.

By continuously observing these KPIs and striving to achieve better outcomes, we can introduce value, get feedback, and mitigate issues quicker. Users are satisfied and engineers motivated. Win:Win!

increasing-stocks-graphic_318-55120-2 | KPIs to increase

  • Deployment Frequency – How many deployments are you making in production? More frequent deployments allow you introduce new value more quickly.

business-down-bars-graphic_318-49908-1 | KPIs to decrease

  • Change Failure Rate - What’s the relation between your changes and outages in production? More successful changes eliminate rework and allows you to focus on new value.
  • Lead Time for Change – What’s your average time between receiving a feature request and deploying it to production? Shorter lead times enable faster feedback and the ability for you to respond to outages more effectively.
  • Mean Time to Recover/Repair (MTTR) – What’s the average time you require to repair a failed component, device, or feature? The lower the better! Faster time to mitigate failures gives your users higher availability.

For example, you phone your service provider to report a problem with your telephone, television, hydro, or other service. You are placed on hold or left listening to soul quenching jingles. “You are 113 in the queue, please be patient. Your call is important to us.” Half an hour later there's a flurry of activity as you are transferred between departments, only to end up on hold again. Patience! Eventually your service provider offers you a fix to your problem. Sound familiar? If yes, you have experienced a common MTTR that’s not delighting end-users. We need to do better!


You should NOT track and evaluate these key performance indicators in isolation. For example, a high deployment frequency is only good news with a low change failure rate! For example continuously and rapidly deploying hotfixes is a serious smell, not something to celebrate!

Remember, we need to continuously monitor and improve these KPIs to achieve better outcomes and delight our end-users with value!