What Are DORA Metrics?
DORA metrics are four software delivery performance indicators — Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Mean Time to Restore (MTTR) — validated by the DevOps Research and Assessment (DORA) team in the annual State of DevOps Report. Teams are classified as Elite, High, Medium, or Low performers based on all four dimensions.
Why DORA metrics matter
The DORA research program (now part of Google Cloud) has surveyed more than 36,000 technical professionals across eight years. Their consistent finding: teams that score Elite across all four DORA dimensions are 2× more likely to exceed organizational performance goals and 2.2× more likely to exceed profitability targets.
Unlike input metrics (story points, hours worked, commits per day), DORA metrics measure delivery outcomes — how fast and reliably software reaches customers. That makes them the standard framework for benchmarking engineering performance across industries.
The four DORA metrics
Deployment Frequency
How often an organization successfully releases to production.
Elite
On-demand (multiple deploys/day)
High
Between once per day and once per week
Medium
Between once per week and once per month
Low
Less than once per month
Higher deployment frequency means smaller batches, lower risk, and faster feedback loops. Elite teams can course-correct within hours.
Lead Time for Changes
Time from a code commit to that code running in production.
Elite
Less than one hour
High
Between one day and one week
Medium
Between one week and one month
Low
More than six months
Short lead times accelerate feature delivery and reduce the cost of defects. Long lead times signal process bottlenecks or large batch sizes.
Change Failure Rate
Percentage of deployments that cause a degradation requiring remediation.
Elite
Less than 5%
High
5–10%
Medium
10–15%
Low
More than 15%
A low CFR means deployments are safe and well-tested. A high CFR indicates insufficient testing, poor code review, or fragile infrastructure.
Mean Time to Restore (MTTR)
How long it takes to recover service after a production incident.
Elite
Less than one hour
High
Less than one day
Medium
Between one day and one week
Low
More than one week
Fast MTTR means the team has strong observability, clear ownership, and practiced runbooks. Slow MTTR compounds customer impact.
How Deviera measures DORA metrics
Deviera computes all four DORA metrics automatically from your GitHub and Vercel integrations — no manual data entry. The free DORA Calculator lets you score your team against benchmarks instantly — no login required. Once you sign up, the DORA Metrics dashboard shows your live tier per dimension with trend comparisons.
Frequently asked questions
What are DORA metrics?
DORA metrics are four software delivery performance indicators validated by the DevOps Research and Assessment (DORA) team: Deployment Frequency (how often code ships to production), Lead Time for Changes (how long it takes for a commit to reach production), Change Failure Rate (percentage of deployments that cause failures), and Mean Time to Restore (how long it takes to recover from a production incident). Teams are classified as Elite, High, Medium, or Low performers based on these four dimensions.
What is an Elite DORA performer?
Elite DORA performers deploy on-demand multiple times per day, have a lead time for changes of less than one hour, a change failure rate below 5%, and a mean time to restore under one hour. These benchmarks are based on the 2024 State of DevOps Report published by Google Cloud DORA.
How do I measure DORA metrics?
DORA metrics are measured from production deployment data, CI/CD pipeline events, and incident records. Deployment Frequency and Lead Time can be derived from Git and CI/CD logs. Change Failure Rate requires tracking which deployments triggered rollbacks or hotfixes. MTTR requires incident duration data from on-call systems. Tools like Deviera compute all four metrics automatically from GitHub, Vercel, and CI/CD integrations.
What is a good change failure rate?
A good change failure rate is below 5% (Elite tier). High performers have a CFR of 5–10%. Medium performers are at 10–15%. Low performers exceed 15%. Change failure rate measures the percentage of deployments that require a rollback, hotfix, or patch within a defined window (typically 24–48 hours).
What is MTTR in DORA metrics?
MTTR (Mean Time to Restore) in DORA metrics measures how long it takes to recover a service after a deployment-caused failure. Elite performers restore service in under one hour. Low performers take more than a week. MTTR is sometimes called Mean Time to Recovery or Mean Time to Repair.
How is DORA different from Agile velocity?
DORA metrics measure delivery performance — how fast and reliably code moves from development to production. Agile velocity measures work throughput in a sprint (story points completed). DORA metrics are output-based and correlate with business outcomes (profitability, market share). Agile velocity is input-based and measures team capacity estimates, which do not predict business results.