Documentation menu
Deployment frequency
What it is
Deployment frequency is one of the four DORA metrics. It measures how often a team delivers code changes to production: the number of deployments divided by the time elapsed, per day, week or month.
Reading it
A higher deployment frequency is generally better: small changes reach production sooner, feedback loops are shorter and the risk per release is lower. A very low frequency usually points at slow or manual processes, missing automation or cultural barriers to change. Deploying very often without the tests and checks to back it up shows up elsewhere: in the change failure rate.
Performance tiers
After the DORA State of DevOps reports, as used on the DORA metrics page:
| Tier | Deployment frequency |
|---|---|
| Elite | On demand, several deployments per day |
| High | Between once per day and once per week |
| Medium | Between once per week and once per month |
| Low | Between once per month and once every six months |
In Agile Analytics
A deployment is a CI/CD pipeline in which a job ran in a production environment, as reported by your Git provider's pipeline webhooks. Pipelines that only deploy to staging, test or acceptance environments do not count. A repository that names no environments at all counts every pipeline. Successful and failed deployments are shown separately. In the health score, delivery uses the median deployments per day per repository over the last 90 days, so one very active repository does not hide the quiet ones.
