Deployment frequency
How often your team successfully deploys to production — the primary DORA throughput metric for software delivery.
// Formula
// About this metric
Deployment frequency measures how often a team successfully releases code to production. It is one of the four key DORA (DevOps Research and Assessment) metrics from the annual State of DevOps Report — the most rigorous longitudinal study of software delivery performance in the industry.
The DORA research found that deployment frequency correlates strongly with both organisational performance and employee wellbeing. Elite performers deploy multiple times per day; low performers deploy fewer than once per month. Crucially, higher deployment frequency is not associated with more incidents — it correlates with lower change failure rates, because small, frequent changes are easier to test, review, and roll back.
The DORA 2024 bands define Elite as multiple deploys per day (≥1/day), High as between once per week and once per day, Medium as between once per month and once per week, and Low as fewer than once per month.
Increasing deployment frequency requires investment in CI/CD automation, feature flags for safe incomplete-feature deployment, and a culture of small, reviewable changes. Teams that deploy infrequently often do so because deployments are risky or manual — addressing the root cause (deployment safety) is more valuable than targeting the frequency number directly.
// Calculator
🧮 Calculator
// Benchmark
Source: DORA State of DevOps Report 2024
// When to use this metric
Use deployment frequency as a throughput health metric in CI/CD-enabled teams. It is most meaningful in teams doing continuous deployment or trunk-based development; it is less useful for teams with infrequent release cycles driven by external constraints such as customer contracts or hardware dependencies.
Track it alongside change failure rate: high frequency with high failure rate means you are deploying fast but unsafely. The goal is high frequency with low failure rate — the Elite DORA profile.
// Common pitfall
Deployment frequency is easy to inflate by deploying configuration changes, documentation updates, or non-production changes. Ensure you are measuring production deployments of meaningful code changes, not all pipeline runs. Teams that game this metric by deploying trivial changes frequently will see their change failure rate and lead time remain poor — the underlying capability hasn't improved.