Deployment Frequency measures how often an engineering team successfully releases code to production. It is a core DORA metric that reflects the maturity of CI/CD practices and the team's ability to deliver value incrementally. Higher deployment frequency correlates with smaller batch sizes, lower risk per release, and faster feedback loops.
How often code reaches production. Elite level: multiple/day; Entry level: monthly+.
In monorepos, per-service deployment frequency can increase due to atomic commits (shipping frontend+backend together). However, naive CI that rebuilds everything becomes a bottleneck, artificially throttling release frequency.
Deployment coordination overhead grows with team size. Elite orgs (Amazon: deploys every 11s) achieve this through architectural decomposition into autonomous teams.
Frequent deploys → no need to batch.
Smaller, frequent deploys reduce risk.
No deployment window waits.
Can't deploy faster than CI allows.
Confident teams deploy more.
Deploy ≠ release enables continuous deployment.
High failure → deployment aversion.
More completed PRs = more deployments. Direct relationship in CD environments.