Deploying more often is useful only if changes remain reliable. Change failure rate is the percentage of deployments that cause a production failure, such as service degradation, an incident, a rollback, or a hotfix. It puts a quality signal beside the speed signal of deployment frequency. section 9.2.4
Read speed and stability together
A team deploying 20 times a week with a 2% change failure rate is in a different position from one deploying three times a week with a 25% rate. Neither deployment count alone describes reliability. If frequency rises while the failure rate holds steady or falls, flow is improving; if both rise, the team is shipping problems faster. section 9.4.1 section 9.2.4
Treat a rising rate as a prompt to inspect the path to production, not as a complete diagnosis. Are reviews being rushed? Has test coverage degraded? Are larger changes being bundled into deployments? Cutting tests to shorten builds can make one metric look better while failures increase. Keep the failure rate visible to the team alongside deployment frequency, and use the pair to judge whether faster delivery is also dependable. section 9.2.4 section 9.3 section 9.4.1
Table 9.3 Paired metrics as guardrails against gaming
|
Speed metric
|
Quality guardrail
|
Gaming looks like….
|
|
Deployment frequency
|
Change failure rate
|
More deploys, more incidents
|
|
Lead time
|
Activity ratio
|
Faster queue clearing, some waiting
|
|
MTTR
|
Incident frequency
|
Faster patching, same root causes
|
|
Cycle time
|
Rework rate
|
Faster merges, more post-merge fixes
|
|
Build time
|
Test coverage
|
Faster builds, fewer tests
|
The paired-metrics table places change failure rate beside deployment frequency as the quality guardrail for more frequent releases. section 9.3




