DORA Metrics

DORA metrics are four measures that show how well a software team ships work and keeps things running. They were developed by the DevOps Research and Assessment (DORA) team -- led by Dr. Nicole Forsgren, Jez Humble, and Gene Kim -- after years of research into what separates high-performing engineering teams from the rest. Google acquired the DORA team in 2018 and continues to publish the annual Accelerate State of DevOps report, which compares thousands of organizations worldwide.

The four DORA metrics are deployment frequency (how often the team ships), lead time for changes (how quickly work gets done and delivered), change failure rate (how often something breaks after shipping), and mean time to recovery (how fast the team recovers when something goes wrong). Together, they give a balanced picture of both speed and reliability. Teams that only optimize for speed risk shipping broken things, while teams that only optimize for reliability move too slowly. DORA metrics track both at once.

What makes DORA metrics especially useful for managers is that they are standardized across the industry. Unlike custom measures that vary from team to team, DORA metrics mean the same thing everywhere. This means you can compare your team's performance against published benchmarks -- Elite, High, Medium, and Low -- and track improvement over time with confidence that you are measuring the right things.

Why DORA Metrics Matter

DORA metrics matter because they are the only widely validated framework for measuring software delivery performance. The research behind them is based on statistical analysis of thousands of organizations across multiple industries and geographies. Unlike opinion-based assessments or vanity metrics like lines of code, DORA metrics correlate directly with organizational outcomes: profitability, market share, and customer satisfaction.

For non-technical managers, DORA metrics translate the abstract question of 'how is our engineering team doing?' into four concrete numbers. Deployment frequency tells you how often your team ships value. Lead time for changes tells you how quickly ideas become reality. Change failure rate tells you how reliable those deliveries are. Mean time to recovery tells you how resilient your team is when things go wrong. Together, these four numbers paint a complete picture of engineering effectiveness.

How to Measure DORA Metrics

Deployment frequency is measured by counting the number of successful deployments to production within a time period. Elite teams deploy on demand, often multiple times per day. Lead time for changes is measured as the time from code commit to that code running successfully in production. Elite teams achieve lead times under one hour.

Change failure rate is the percentage of deployments that result in a degraded service or require a rollback, hotfix, or patch. Elite teams maintain change failure rates below 5 percent. Mean time to recovery measures how long it takes to restore service after a production incident. Elite teams recover in under one hour. Most engineering analytics tools, including CodeVitals, calculate these metrics automatically from your version control and deployment data.

Common Mistakes When Adopting DORA Metrics

The most common mistake is treating DORA metrics as individual performance measures rather than team-level indicators. DORA metrics are designed to assess organizational and team capability, not to rank individual developers. Using them to evaluate individuals creates perverse incentives: developers will game deployment frequency by shipping trivially small changes or avoid risky refactoring that might increase change failure rates.

Another frequent error is optimizing a single metric in isolation. Increasing deployment frequency without monitoring change failure rate can lead to shipping broken code faster. Reducing lead time by skipping code review compromises quality. DORA metrics are designed to be used as a balanced scorecard where improvement in one area does not come at the expense of another.

Related Metrics

DORA metrics connect to several other concepts in engineering analytics. Cycle time is closely related to lead time for changes but measures only the development process (commit to merge), not the full deployment pipeline. Developer velocity is a broader concept that encompasses DORA metrics alongside team throughput and process efficiency. Engineering team health extends beyond delivery metrics to include collaboration patterns, knowledge distribution, and sustainability indicators.

Understanding how these metrics relate to each other helps engineering leaders build a comprehensive measurement strategy rather than relying on any single framework.

Key Takeaways

• •DORA metrics are four standardized measures of software delivery performance: deployment frequency, lead time for changes, change failure rate, and mean time to recovery.
• •They were developed through rigorous research and correlate with organizational outcomes like profitability and customer satisfaction.
• •DORA metrics should be used as team-level indicators, never as individual performance measures.
• •All four metrics should be tracked together as a balanced scorecard -- optimizing one at the expense of others defeats the purpose.
• •Elite performance benchmarks: deploy on demand, lead time under one hour, change failure rate under 5%, recovery in under one hour.

How CodeVitals Helps

CodeVitals tracks these four areas automatically by connecting to your GitHub repositories. Instead of asking your engineering team to manually calculate and report metrics, you get a real-time health score that turns these signals into a single verdict any manager can read in 30 seconds. You see plain-language coaching recommendations -- not charts that require a technical background -- so you know exactly what to improve first.

Related Reading