100% Free Forever
AI-Powered Learning
Industry Expert Content
Certificates & Badges
Learn At Your Own Pace
DevOps

DORA Metrics

DevOps Research and Assessment framework

IntermediateConcept9.8K learners

DORA metrics are a set of four key indicators — deployment frequency, lead time for changes, change failure rate, and mean time to recovery — used to measure software delivery and operational performance.

Definition

DORA metrics are a set of four key indicators — deployment frequency, lead time for changes, change failure rate, and mean time to recovery — used to measure software delivery and operational performance.

Overview

DORA metrics come from the DevOps Research and Assessment (DORA) program, a multi-year research effort, later acquired by Google, that surveyed tens of thousands of engineering professionals to identify which practices actually predict organizational performance. Its findings, published in the "Accelerate" book and annual State of DevOps reports, established four metrics as statistically reliable indicators of elite software delivery: deployment frequency and lead time for changes (speed), and change failure rate and mean time to recovery (stability). The central insight of the DORA research is that speed and stability are not a trade-off — teams that deploy more often, with shorter lead times, also tend to have fewer failures and faster recovery, because the practices that enable frequent, low-risk deployment (automated testing, small batch sizes, trunk-based development, monitoring, and fast rollback) are the same practices that make software more stable. This challenged a common assumption that moving fast necessarily means breaking more things. DORA classifies organizations into four performance tiers — elite, high, medium, and low — based on where they fall across the four metrics, giving teams a benchmark to compare against industry data rather than arbitrary internal targets. Many engineering organizations now track DORA metrics on dashboards fed by CI/CD pipelines, version control systems, and incident management tools, using platforms like GitHub, GitLab, or purpose-built DORA analytics tools to automate the calculation. While useful, DORA metrics are explicitly a proxy for delivery performance, not a complete picture of engineering health — they say little about code quality, developer experience, or product outcomes, so most teams pair them with other metrics like developer satisfaction surveys or SPACE framework indicators.

Key Concepts

  • Four metrics: deployment frequency, lead time for changes, change failure rate, MTTR
  • Derived from large-scale, multi-year DevOps research surveys
  • Split into speed metrics (frequency, lead time) and stability metrics (failure rate, MTTR)
  • Classifies organizations into elite, high, medium, and low performance tiers
  • Shows that delivery speed and stability improve together, not at odds
  • Documented in the 'Accelerate' book and annual State of DevOps reports
  • Commonly tracked via CI/CD, version control, and incident data
  • Now stewarded largely under Google Cloud's DevOps research umbrella

Use Cases

Benchmarking engineering team performance against industry data
Identifying which delivery practices to invest in next
Building executive dashboards for engineering leadership
Guiding platform engineering and internal developer platform investments
Supporting data-driven conversations about process changes

Frequently Asked Questions

From the Blog