What the bands mean
Every number counts back from the time in the footer: deployment frequency from the successful deployments, lead time for changes from the commits they shipped, failed deployment recovery time from the failed deployments and the successful ones after them, change fail rate from the failed deployments and the issues labelled failure, deployment rework rate from the successful deployments that came after a failed deployment or while a failure issue was open.
A project's total row counts all its repositories; a row under it counts what its label names in the project's config. Durations: min is minutes, h hours, d days, each cut down, never rounded up.
Deployment frequency
The DORA band, then the successful deployments of the last 30 days, or of the last 180 days when the 30 days hold none:
- On demand (multiple deploys per day): 720 and more in 30 days
- Between once per hour and once per day: 30 to 719 in 30 days
- Between once per day and once per week: 5 to 29 in 30 days
- Between once per week and once per month: 1 to 4 in 30 days
- Between once per month and once every six months: none in 30 days, 1 and more in 180 days
- Less than once per six months: none in 180 days
Lead time for changes
The DORA band, then the median time from a commit to the successful deployment that shipped it, and in brackets the commits deployed in the last 30 days. A month is 30 days:
- Less than one hour: below 1 hour
- Less than one day: 1 hour to below 24 hours
- One day to one week: 24 hours to below 7 days
- One week to one month: 7 days to below 30 days
- One to six months: 30 days to below 180 days
- More than six months: 180 days and more
Failed deployment recovery time
The DORA band, on the edges of lead time for changes, as the DORA Quick Check gives both the same answers; then the median time from the first failed deployment of a run to the next successful deployment of the same stream, and in brackets the recoveries of the last 30 days; then the recoveries not completed yet, each a run of failed deployments with no success after it, counted, not timed. With none completed, the band and the median are —.
Change fail rate
The DORA band, the nearest label of the DORA Quick Check's scale; then the failed changes out of the final deployments of the last 30 days, in whole percent, rounded down, and in brackets both counts. A failed change is a failed deployment or an issue labelled failure opened in the window, per repository the larger of the two counts, so an issue about a failed deployment is not counted twice. A failure issue names no service, so a service's row counts its failed deployments only.
- 0%: below 10%
- 20%: 10% to below 30%
- 40%: 30% to below 50%
- 60%: 50% to below 70%
- 80%: 70% to below 90%
- 100%: 90% and more
Deployment rework rate
The DORA band, on the six points and edges of change fail rate, as the DORA Quick Check scales both the same; then the rework deployments out of the successful deployments of the last 30 days, in whole percent, rounded down, and in brackets both counts. A rework deployment is a successful deployment that is the first success of its stream after a failed deployment, or that happened while an issue labelled failure of its repository was open; it is counted once. A failure issue names no service, so a service's row counts the first kind only. DORA's question is "Approximately what percentage of deployments in the last 6 months were not planned but were performed to address a user-facing bug in the application?", but forsgren measures the last 30 days, like its other four metrics.