DORA Metrics
The four software delivery metrics with a validated link to business outcomes — deployment frequency, lead time for changes, change failure rate and time to restore — measured automatically from the tools your teams already use.
What are DORA metrics?
DORA metrics are four measures of software delivery performance identified by the DevOps Research and Assessment (DORA) program through a decade of research across tens of thousands of engineering teams. They are the only widely adopted engineering metrics with a research-validated correlation to organizational performance: teams that score well on them ship more value, more reliably.
The four metrics split into two pairs. Deployment frequency and lead time for changes measure throughput — how often and how fast your teams turn work into running software. Change failure rate and time to restore service measure stability — how often changes break production and how quickly you recover when they do. High-performing teams improve both pairs together; the research consistently shows speed and stability are not a trade-off.
Tracked continuously, the four metrics give engineering and executive stakeholders a shared, objective language for delivery health — grounded in what actually happened in version control, CI/CD and incident tooling, not in status reports.
The four key metrics, defined
Deployment frequency
How often your organization successfully releases to production. A direct read on batch size and flow: teams that deploy small changes often carry less risk per release and get feedback sooner.
Elite: on-demand — multiple deploys per dayLead time for changes
The time from a commit landing in trunk to that change running in production. It exposes every queue in your delivery system — review wait, build time, test time, approval gates, release windows.
Elite: under one dayChange failure rate
The percentage of production changes that result in degraded service and need remediation — a hotfix, rollback or patch. It is the stability counterweight to deployment frequency.
Elite: ~5% of changesTime to restore service
How long it takes to recover when a change does cause a production failure. Reversible deploys, good observability and rehearsed incident response compress it.
Elite: under one hourAutomated DORA telemetry
No spreadsheets, no self-reporting. The platform derives all four metrics continuously from git activity, CI/CD pipelines and incident tooling — normalized across every team, repo and vendor on one governed data layer.
Successful production deploys, rolling 30-day median.
Commit-to-production, median across active repos.
Deploys needing hotfix or rollback, rolling window.
Median time from incident open to service restored.
What the platform does with them
Measurement is the floor. The platform turns the four metrics into an operating instrument — benchmarked, segmented and wired into the same control plane that orchestrates your agents, talent and delivery.
Automated collection
Metrics derive from system events, not surveys.
Benchmarking & targets
Every metric lands against the elite / high / medium / low research bands.
Executive reporting
One rollup for technical and business stakeholders.
Bottleneck detection
Lead-time decomposition shows where flow actually stalls.
Stability guardrails
Change failure rate and restore time feed live health gates — alongside platform reliability itself.
Orchestration context
DORA reads sit beside the work itself — agents, teams, deployments.
How measurement works
From connect to rollup in under an hour — the same onboarding as the rest of the platform, because it is the same platform.
Connect your tools
Authorize read access to version control, CI/CD and incident tooling. No migration, no workflow change.
Normalize the signal
The platform maps commits, pipelines, deploys and incidents onto one event model across every team and vendor.
Watch the four metrics land
Deployment frequency, lead time, change failure rate and time to restore compute continuously against research benchmarks.
Improve with the platform
Use orchestrated agents, quality gates and delivery intelligence — the rest of this platform — to move the numbers.
Software delivery performance bands (DORA research)
| Metric | Elite | High | Medium | Low |
|---|---|---|---|---|
| Deployment frequency | On-demand (multiple per day) | Daily to weekly | Weekly to monthly | Monthly or slower |
| Lead time for changes | Under one day | One day to one week | One week to one month | Over one month |
| Change failure rate | ~5% | ~10% | ~15% | Above 15% |
| Time to restore service | Under one hour | Under one day | One day to one week | Over one week |
Bands per the DORA Accelerate State of DevOps research program. The platform scores every team against these bands automatically.
How DORA metrics relate to developer productivity
DORA metrics measure the delivery system — how often and how safely change reaches production. They deliberately say nothing about individual activity, and they stop at the pipeline: they tell you that lead time is rising, not why.
Developer productivity is the wider workflow question — cycle time, review flow, churn and quality across everything that happens before a change ships. Because the platform computes both from the same event model, a lead-time regression traces straight to its cause — most often a review queue — in developer productivity analytics across teams, tools and agents.
The same telemetry also feeds the forward-looking question of engineering capacity planning: whether the teams behind these delivery numbers actually have the capacity the roadmap assumes.
DORA Metrics — frequently asked questions
What are the four DORA metrics?
Deployment frequency (how often you release to production), lead time for changes (commit to production), change failure rate (the percentage of changes that degrade service) and time to restore service (how fast you recover from failures). The first two measure throughput, the second two measure stability.
Where do DORA metrics come from?
From DORA — the DevOps Research and Assessment program — whose Accelerate State of DevOps research has studied software delivery performance across tens of thousands of teams for around a decade, and found these four metrics predict organizational performance.
What is a good deployment frequency?
Elite performers deploy on demand, typically multiple times per day. High performers deploy between daily and weekly. More important than the absolute number is the trend: smaller batches deployed more often reduce risk per change and shorten feedback loops.
How are DORA metrics measured automatically?
By deriving them from system events instead of surveys: deploys and lead time from version control and CI/CD pipelines, change failures and restore time from incident and rollback signals. The platform normalizes those events across every connected tool and computes all four continuously.
Do DORA metrics trade speed against stability?
No — that is the central research finding. Teams that deploy more frequently also tend to have lower change failure rates and faster recovery, because the same practices (small batches, automation, good observability) drive both.
DORA vs SPACE: which should we use?
They answer different questions. DORA measures software delivery performance; SPACE is a broader framework for developer productivity and experience. Most teams start with DORA because it is objective, automatable and benchmarked, then layer SPACE-style signals on top.
How do we improve our DORA metrics?
Reduce batch size, automate the path to production, add progressive delivery with health gates, and make rollback cheap. On this platform those levers are built in — orchestrated AI agents for review and testing, unified pipelines with quality gates, and live delivery intelligence to show where flow stalls.
Is DORA metrics tracking priced separately?
No. DORA metrics are a capability of the Scrums.com platform, included in the platform subscription alongside every other capability — there is no separate analytics product or per-capability pricing.
More platform capabilities
Every capability below ships in the same bundled subscription — one platform, one plan, nothing sold piecemeal.
One platform. One subscription.
DORA Metrics included.
DORA Metrics isn't a product you buy separately — it's one capability of the Software Engineering Orchestration Platform, bundled with every other capability on this page.