Industry Trends & Thought Leadership

Speed and Stability Are Not a Trade-off: Measuring Software Team Performance with DORA Metrics

DORA research repeatedly shows that the best teams are both fast and stable. Learn the five software delivery performance metrics and how to use them wisely.

By Oemah Solution Editorial Updated 3 min read

This article was translated from Bahasa Indonesia with AI assistance and reviewed by our team.

Hands typing on a laptop displaying code on a wooden desk
Photo: Programmer at work (Unsplash) by Crew crew · CC0 · Wikimedia Commons

Many organisations still see software development as a tug-of-war between speed and safety: more frequent releases are assumed to mean more problems, so changes are held back and bundled into large, infrequent releases. DevOps Research and Assessment (DORA) research shows that this view is mistaken.

The key finding: the two go together

According to DORA, its research repeatedly shows that speed and stability are not a trade-off. For most teams, the speed and stability metrics are in fact correlated: teams that can ship changes quickly also tend to be more stable. DORA quotes Dave Farley: the real trade-off, in the long run, is between better and faster software, or worse and slower software.

The reasoning makes sense: small changes that are released often are easier to test, easier to trace when something goes wrong, and easier to roll back.

Five software delivery performance metrics

DORA now uses five metrics, grouped into two categories:

Throughput — how much change flows through the system:

  1. Change lead time — the time it takes for a change to go from being committed to version control to running in production.
  2. Deployment frequency — the number of deployments in a given period, or the interval between deployments.
  3. Failed deployment recovery time — the time to recover from a failed deployment that requires immediate intervention.

Instability — how well deployments go:

  1. Change fail rate — the ratio of deployments that require immediate intervention after release.
  2. Deployment rework rate — the ratio of unplanned deployments that occur as a result of production incidents.

Using metrics wisely

These metrics are powerful, but easy to misuse. Some principles we follow:

  • For improvement, not punishment. Once a metric becomes an individual target, people will optimise the numbers rather than the outcomes.
  • Compare a team with itself. Every application has a different context; trends over time are more meaningful than comparisons between teams.
  • Look at all five together. Raising deployment frequency without watching the change fail rate only moves the problem elsewhere.
  • Automate the measurement. Data from CI/CD pipelines and incident systems is more honest than manual reports.

What this means for project owners

For organisations that use external developers, DORA metrics provide a shared language that is more useful than simply asking "when will it be done". Some questions worth asking the development team:

  • How long does it take for a small fix to reach users?
  • How often is the application released, and is the process automated?
  • If a release goes wrong, how long does it take to recover?
  • What percentage of releases require an emergency fix?

The answers to these questions describe the health of the development process far better than the number of features in a specification document. In an era when business needs change quickly, the ability to ship small changes safely and often is a competitive advantage — not a luxury.

#thought leadership#devops#dora#project management

Sources & references

This article is a summary and interpretation by the Oemah Solution team of the sources below. Refer to the original sources for full details and context.

  1. DORA's software delivery performance metrics DORA · dora.dev
  2. DORA Research Program DORA · dora.dev