What Are DORA Metrics?
Four key metrics that measure software delivery performance: deployment frequency, lead time for changes, change failure rate, and mean time to recovery (MTTR).
2-minute setup • No credit card required
What it means
DORA metrics were developed by the DevOps Research and Assessment (DORA) team at Google, based on over a decade of research into what makes high-performing software teams. The four metrics measure two aspects of delivery: speed (deployment frequency and lead time) and stability (change failure rate and MTTR). Research consistently shows that elite teams score high on all four — speed and stability are not tradeoffs. Teams that deploy more frequently also tend to have fewer failures and recover faster. DORA metrics have become the industry standard for benchmarking engineering team performance because they're objective, measurable from git and deployment data, and correlate with business outcomes.
Why DORA Metrics matter
DORA metrics give engineering leaders a data-driven way to measure team performance without resorting to vanity metrics like lines of code or commit counts. They connect engineering work to business outcomes: teams with elite DORA scores ship features faster, have less downtime, and spend less time on firefighting. For CTOs and VPs, DORA metrics provide a common language to discuss engineering performance with non-technical executives. For engineering managers, they highlight specific bottlenecks (slow reviews, unstable deployments) that can be improved with targeted process changes.
How to measure
Deployment Frequency: count how often your team deploys to production per week/month. Pull this from your CI/CD system or git tags. Lead Time for Changes: measure the time from first commit on a branch to that code running in production. This includes coding, review, and deployment time. Change Failure Rate: divide the number of deployments that cause incidents by total deployments. Track this via your incident management tool. Mean Time to Recovery (MTTR): measure the time from incident detection to resolution. Requires linking incident timestamps to the fix commit/deployment.
Real-world example
A SaaS startup measures their DORA metrics and finds: Deployment Frequency is 12/week (elite), Lead Time is 4 days (medium — their PR reviews take 2+ days), Change Failure Rate is 2% (elite), and MTTR is 6 hours (high). The bottleneck is clearly in code review turnaround. By setting up automated PR reminders and distributing review load more evenly, they reduce lead time to 1 day within a month — without sacrificing their already-low failure rate.
Related terms
Common questions
What are the four DORA metrics?
The four DORA metrics are: (1) Deployment Frequency — how often you deploy to production, (2) Lead Time for Changes — time from commit to production, (3) Change Failure Rate — percentage of deployments causing failures, and (4) Mean Time to Recovery — how quickly you recover from failures.
What are the DORA metrics benchmark levels?
DORA classifies teams into four levels: Elite (deploy on-demand, lead time under 1 day, CFR under 5%, MTTR under 1 hour), High (deploy weekly, lead time 1 day to 1 week, CFR 5-10%, MTTR under 1 day), Medium (deploy monthly, lead time 1 week to 1 month, CFR 10-15%, MTTR under 1 week), and Low (deploy less than monthly, lead time over 1 month, CFR over 15%, MTTR over 1 week).
How do you track DORA metrics automatically?
DORA metrics can be tracked by connecting your git platform (GitHub, GitLab, Bitbucket) to a reporting tool that correlates commits, PRs, and deployments. Tools like Gitmore, Sleuth, and Swarmia can calculate these metrics automatically from your existing git workflow. The key requirement is linking deployment events to the code changes they contain.
Are DORA metrics relevant for small teams?
Yes. DORA metrics are especially valuable for small teams because they highlight bottlenecks that small teams can't afford. If your 5-person team has a 3-day lead time because of slow reviews, that's a bigger relative impact than for a 50-person team. Small teams can also improve their DORA scores faster because there's less organizational inertia.
Do DORA metrics replace other engineering metrics?
No. DORA metrics measure delivery performance specifically. They don't cover code quality, developer experience, or business impact directly. Many teams combine DORA with the SPACE framework (Satisfaction, Performance, Activity, Communication, Efficiency) for a more complete picture. DORA is the delivery lens; you still need other metrics for quality and team health.
Track DORA Metrics Automatically
Gitmore turns your git activity into automated reports with real metrics — delivered to Slack and email.
Get Started FreeNo credit card • No sales call • Reports in 2 minutes