Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →DORA’s current software delivery performance model has five metrics, not four: change lead time, deployment frequency, failed deployment recovery time, change fail rate, and deployment rework rate. Three describe throughput and two describe instability. DORA says to calculate them for one application or service at a time and to track each service’s trend against its own baseline. They are not a context-free league table.
The five DORA metrics at a glance
DORA’s guide to software delivery performance metrics, written by Nathen Harvey for DORA and Google Cloud, groups the measures like this:
As an Amazon Associate I earn from qualifying purchases.
| Metric | Group | DORA definition | What to pin down on your team |
|---|---|---|---|
| Change lead time | Throughput | Time for a change to move from commit in version control to production deployment. | Use the same start event (commit) and end event (running in production) for every change. |
| Deployment frequency | Throughput | Number of deployments over a period, or time between deployments. | Choose one form, a count per fixed period or an interval, and stick to it. |
| Failed deployment recovery time | Throughput | Time to recover from a failed deployment that requires immediate intervention. | Count recovery tied to a production change that impaired service, not every unrelated incident. |
| Change fail rate | Instability | Ratio of deployments that require immediate intervention after deployment, likely a rollback or hotfix. | Write down which failures and remediations qualify. |
| Deployment rework rate | Instability | Ratio of deployments that are unplanned and happen because of a production incident. | DORA’s survey wording asks about the share of deployments in the past six months that were unplanned and addressed a user-facing bug. |
Recovery time sits with throughput in DORA’s grouping even though it concerns failure, so don’t file it under instability.
Taken together, the measures show how quickly changes flow and how often that flow causes trouble. A team can deploy often and still be unstable, so a high deployment count is not success on its own. DORA states that “speed and stability are not tradeoffs” and reports that the measures tend to correlate for most teams.
#1 Best Overall
- Every page is grease and tear-proof & FULL color
- Portable and fits into the pocket -take it everywhere!
- It is wiro layflat bound so it stays open unassisted
- Metric Sizing, 3rd Edition, Handbook/Pocket Size
- Free set of self-adhesive index tabs
Why you still see “four keys” in older material
How the model evolved
According to DORA’s “A history of DORA’s software delivery metrics” (updated January 2, 2026), the original model had four measures: deployment frequency, lead time for changes, time to recover, and change fail rate. Recovery was later narrowed from broad MTTR or time-to-restore wording to failed deployment recovery time, so that it reflects impairment caused by a production change. In 2024 DORA added deployment rework rate, which made five.
Which source to cite for what
- The Accelerate State of DevOps Report 2024 (version 2024.3) has a section titled “The four keys”: deployment frequency, change lead time, change fail rate, and failed deployment recovery time. Use it when describing the earlier framework.
- Use DORA’s current metrics guide and its April 22, 2026 “Quick Check updates” post when describing the current model.
Where reliability fits
DORA treats reliability as an operational performance measure, separate from the software delivery metrics. Service-level targets and service health are useful context. They do not replace deployment rework rate in the five delivery metrics.
How to measure DORA metrics
- Pick one primary application or service. DORA says the metrics suit one application or service at a time. Record the service boundary so later comparisons mean something.
- Agree on event definitions. Decide what counts as a production deployment, a failed deployment, a qualifying intervention, and an unplanned remedial deployment. DORA’s questionnaire anchors its questions to the primary service and uses examples such as hotfix, rollback, fix forward, and patch.
- Set a baseline. Use DORA’s Quick Check as a conversation starter. If team members answer differently or are surprised by the result, work out why before choosing what to fix.
- Read the two groups together. Lead time, deployment frequency, and recovery time on one side; change fail rate and rework rate on the other. Improving one group at the other’s expense is a warning sign.
- Choose a specific improvement outcome. DORA’s value stream mapping guidance recommends stating the outcome concretely, then mapping the work from commit to production, or mapping the recovery path after an incident. Find the bottleneck and test one focused change.
Plain-language questions that mirror the survey
These come from DORA’s research instrument and work well as internal check-in questions:
Recommended Free Tools
- “How often does your organization deploy code to production or release it to end users?”
- “What is your lead time for changes (i.e., how long does it take to go from code committed to code successfully running in production)?”
- For recovery: how long does it generally take to restore service after a production change causes degraded service and requires remediation?
Using the Quick Check
DORA’s April 22, 2026 update describes an assessment with five individual metrics, an overall score normalized to a 0–10 scale, separate throughput and stability scores, and comparison benchmarks derived from DORA’s 2025 research program. DORA’s guidance is to treat the score as a prompt for discussion about what is holding the team back. It is not a grade.
Rank #3
- Every page is grease and tear-proof
- It is wiro layflat bound so it stays open unassisted
- Full color for easy reading
- Large, workbench edition. Metric Sizing
- Free set of self-adhesive index tabs
Comparing teams and services without misleading anyone
- Scope: Compare only services with comparable production boundaries and user context.
- Throughput: State definitions and measurement windows for lead time and deployment frequency.
- Instability and recovery: Apply the same rules for “intervention” and “incident-related work” everywhere.
- Trend: The most defensible comparison is a service against its own earlier results.
Don’t promise that moving a single metric will produce a specific business result. DORA frames the metrics as a way to understand change over time and choose improvement work, not as proof of causation. A deployment count that rises while fail rate or rework rate also rises means the system has become less stable, not faster in any useful sense.
Quick Recap
Best Value
- SOLID ALUMINUM 30cm METRIC - Engineer, Mechanical, Architectural, Draftsman scale ruler with triangular body for safer cutting and scoring of materials.
- PRECISE SCALES - 1:20, 1:25, 1:50, 1:75, 1:100, 1:125. For professional applications, architecture, engineering, and technical Illustration
- PRECISION MARKED METRIC GRADATIONS (NOT IMPERIAL) - Easy-to-read printed gradations.
- 3 SIDES with 6 METRIC SCALES - Concave base reduces smearing when drawing.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
