---

Change failure rate rating table

Description	Elite	High	Medium	Low
For the primary application or service you work on, what percentage of changes to production or releases to users result in degraded service (e.g. lead to service impariment or service outage), and subsequently required remediation (e.g. require a hotfix, rollback, fix forward, patch)	0-15%	0-15% (although we are using 16-30% for this calcuation)	0-15% (although we are using 31-45% for this calcuation)	46-60% (although we are using 46%+ for this calculation)

---

FAQ
What am I looking at?
Change failure rate is a high performing DevOps metric to measure the success of deployments to production. This page helps us to measure it across various projects in both Azure DevOps and GitHub
How does it work?
We look at builds, and let the user indicate if it was successful or a failure. By default (currently), the build is considered a failure. (We are going to change this to success by default later)
Assumptions/things we can't currently measure:
- The build is multi-stage, and leads to a deployment in a production environment.
- We only look at a single branch (usually the main branch), hence we ignore feature branches (as these probably aren't deploying to production)
- The user has reviewed the build/deployment and confirmed that the production deployment was successful