-
Notifications
You must be signed in to change notification settings - Fork 3
/
params.json
6 lines (6 loc) · 2.55 KB
/
params.json
1
2
3
4
5
6
{
"name": "Measuring DevOps Flow",
"tagline": "12 DevOps/CI/CD KPIs as defined by Otomato",
"body": "## Introduction\r\nDevOps transformation goals can be defined as:\r\n * Heightened Release Agility\r\n * Improved Software Quality\r\n\r\nOr simply:\r\n\r\n***\r\n\r\n# Delivering Better Software Faster\r\n\r\n***\r\n\r\nTherefore measurable DevOps success criteria would be:\r\n * Being able to release versions faster and more often\r\n * Having less defects and failures\r\n \r\nWe all know that improvement doesn't happen overnight, but instead is an iterative, continuous process.\r\nWe want to be able to measure our improvement by applying a scientific step sequence of hypothesis->attempt->analysis->proceed on the outcome->...\r\n\r\nIn order to measure DevOps flow improvement we need to have metrics for 2 categories:\r\n * __Velocity__ (time it takes to complete each step in the release/delivery cycle, number of releases per time period.)\r\n * __Quality__ (rate of defects per change, etc)\r\n\r\nHere are the 12 core KPIs we've come up with. 6 for Velocity and 6 for Quality:\r\n\r\n## Velocity KPIs\r\n\r\n1. __MLT__ (Mean Lead Time)\t \r\nhow long does it take for a bit of code to get built, tested and deployed.\r\n2. __DCR__ (Daily Change Rate) \t\r\nnumber of changes getting committed to mainline and tested per day.\t\r\n3. __MTTE__ (Mean Time To Environment) \t\r\nhow much time it takes developers/testers to bring up a testing environment for verifying each delivered change.\t\"\r\n4. __MTTD__ (Mean Time to Detect) \t \r\nhow much time passes since the original commit of code until the bug it introduces gets detected.\r\n5. __MTTR__ (Mean Time To Resolve) \t\r\nhow much time it takes to resolve an issue after it’s detected\r\n6. __MTTA__ (MeanTime To Approve)\t \r\nhow much time it takes to approve and verify a release. (Measured from the moment all release content has been delivered and until the release has passed all the defined test and verification cycles)\r\n\r\n## Quality KPIs\r\n\r\n1. __BFR__ (Build Failure Rate)\r\n \t% of failed builds\t\t\r\n2. __DFR__ (Deployment Failure Rate)\r\n \t% of failed deployments\t\t\r\n3. __IRFR__ (Infrastructure-Related Failure Rate)\r\n% of build/deployment failures related to infrastructure issues\r\n4. __RWR__ (Rework Rate)\r\n% of tickets being reopened\r\n5. __ADR__ (Automated Detection Rate) \t\r\n% of defects being detected by automated testing cycles.\tQA\t\r\n6. __UWR__ (Unplanned Work Rate)\r\n% of unplanned issues",
"note": "Don't delete this file! It's used internally to help with page regeneration."
}