DORA metrics are the industry-standard measures of software delivery performance, popularized by Google's DevOps Research and Assessment program. Leanmote tracks all four out of the box on the Software Delivery Performance tab of the Performance Delivery dashboard.
The four DORA metrics
Deployment Frequency — how often you ship to production. A speed metric.
Lead Time for Changes — how long a change takes to reach production. Another speed metric.
Mean Time to Recovery (MTTR) — how quickly you restore service after an incident. A stability metric.
Change Failure Rate — what percentage of deployments cause incidents. A quality metric.
Read in pairs, the four metrics balance speed against stability. Improving one without breaking the other is the goal.
Why they matter
DORA's research correlates these four metrics with overall software-delivery performance and, indirectly, with business outcomes. Teams that score well on all four tend to ship faster and recover quicker than peers. Tracking them gives you a defensible, externally validated benchmark.
What Leanmote needs to calculate them
Source-control integration (GitHub, GitLab, etc.) for commit and PR timestamps.
Deployment events from your CI/CD or deployment tool — for Deployment Frequency and Lead Time.
Incident events from your incident management tool or marker labels — for MTTR and Change Failure Rate.
If incident data isn't connected, MTTR and Change Failure Rate stay empty. See Why a metric looks off.
How to read DORA in a review
Look at Deployment Frequency first — direction over the last 4 weeks.
Pair it with Lead Time. Frequent deploys with rising lead time means batch sizes are growing.
Validate quality with Change Failure Rate. If speed climbs but failure rate climbs too, you're trading.
End with MTTR. A high failure rate is more tolerable when recovery is fast.
Related articles
Deployment Frequency
Lead Time for Changes
Mean Time to Recovery
Change Failure Rate
Performance Delivery dashboard