Software Delivery in a Minute
Deployment Frequency
What deployment frequency measures, how teams calculate it, and what it cannot tell you alone.
In one sentence
Deployment frequency is how often an organization successfully releases changes to a target environment in a time window.
Why it matters
It is a core DORA throughput signal. Used alone, it can reward noisy deploys or punish careful batching without showing customer outcomes.
How it works
- Define the environment (production vs staging) and what counts as a deployment.
- Count successful deploys in a period, or measure average time between deploys.
- Compare trends inside one system before comparing across unlike products.
- Read it next to change failure rate and recovery time—not in isolation.
Example
If production deploys succeeded on 12 distinct days in a 30-day month, a simple daily-success view is “about every 2.5 days.” Hotfix and empty calendar pushes both affect the story—document what you counted.
What this proves
Deployment frequency proves how often your defined deploy events occurred in the window.
What this does not prove
It does not prove feature value, code quality, developer productivity, or that faster is always better for your risk profile.
Sources
Last reviewed 2026-09-06. Title for citation: Software Delivery in a Minute: Deployment Frequency.