Change Failure Rate: Failures by Severity are More Useful Than a Rate
The Change Failure Rate metric, as defined by DORA, is a useful indicator of the stability percentage of the software delivery process. However, we recommend organizations may find more value in tracking specific failures, defects, or bugs that impact customers or business operations because these failures are more directly actionable, as well as repairable.
Set Up Change Failure Rate in Allstacks
There are several ways to set this up but the most straightforward is to configure a velocity metric that compares the number of incidents dealt with per week versus the number of normal items completed. Go to Team Productivity > Velocity > By Type, No Team Filter. Use the Advanced Filters dialog to filter out statuses and item types that aren’t relevant. These are often “won’t do” statuses and card types such as “subtasks” or types that represent non-code work. Use Chart Settings to select a Grouped Column chart so that the volumes of different types of items per week can be compared. For your series option, select the field that indicates the severity of your incidents. We recommend you add annotations for your typical number of items released per week as well as a threshold under which the volume of escapes should stay.
Below is a step by step example.