DORA metrics are four key measures of software delivery performance developed by the DevOps Research and Assessment program, a multi-year research effort that surveyed tens of thousands of engineering teams to identify what distinguishes high performers from low performers. The four metrics are deployment frequency (how often code is deployed to production), lead time for changes (how long it takes a commit to reach production), change failure rate (what percentage of deployments cause a production incident), and time to restore service (how long it takes to recover when an incident occurs).
The research found that these four metrics cluster together predictably. Teams that deploy frequently also have short lead times, low failure rates, and fast recovery. Teams that deploy infrequently tend to have long lead times, higher failure rates, and slower recovery. The metrics are not independent levers; they reflect the overall health of the engineering system, including practices, tooling, team structure, and culture.
For technical and non-technical leaders, DORA metrics provide a language for discussing engineering performance without getting lost in proxy metrics that are easy to game, such as lines of code written or story points completed. A team can increase its story point velocity while its DORA metrics worsen, which is a warning sign. A team improving on all four DORA dimensions is genuinely improving its ability to deliver reliable software quickly.
The metrics are most useful as directional indicators over time rather than as absolute benchmarks to hit. Industry classifications (elite, high, medium, low) exist, but the more valuable question for most organizations is whether the numbers are improving month over month as the team invests in engineering practices.