liveBook · Manning

Change failure rate

Change failure rate is the proportion of deployed software changes that cause failures requiring remediation, rollback, recovery, or other corrective action.

How 5 Manning books explain it

Build High Value Software Systems

The proportion of software changes that cause a failure requiring remediation, rollback, or another corrective response.

How it is used
Acts as a production-quality guardrail when assessing deployment frequency and software delivery flow.
How deep it goes
Defines the percentage, interprets paired trends, and offers diagnostic questions rather than a data-collection procedure.
Examples
Contrasts teams deploying 20 times weekly at 2% failure and three times weekly at 25%, and considers failures hidden by faster builds.
What you can do after
Evaluate/understand whether faster deployments represent better flow or merely introduce more production failures.

Read how Build High Value Software Systems explains change failure rate →

Effective Platform Engineering

Change failure rate is the proportion of software deployments that cause a failure requiring remediation, rollback, or another corrective action.

How it is used
Measures deployment reliability across environments and shows whether platform or application changes affect end users.
How deep it goes
Tracks failures from development through production and pairs the lagging percentage with leading quality and remediation indicators.
Examples
Uses development, QA, preview, and production environments plus Epetech’s quality, testing, and rollback measurements.
What you can do after
Evaluate deployment reliability, identify pipeline quality risks, and focus improvement where failures most threaten users.

Read how Effective Platform Engineering explains change failure rate →

Platform Engineering on Kubernetes

Change failure rate is the proportion of software deployments that require remediation because they cause failures or degradations in production.

How it is used
Uses change failure rate to evaluate delivery reliability and determine whether platform improvements support continuous delivery.
How deep it goes
Explains the metric’s role and a collection pipeline, but does not provide a detailed calculation formula or remediation policy.
Examples
Uses event sources, CloudEvents normalization, Knative Serving functions, PostgreSQL storage, and dashboards as pipeline components.
What you can do after
Calculate change failure rate by collecting, standardizing, storing, processing, and presenting delivery events.

Read how Platform Engineering on Kubernetes explains change failure rate →

Grokking Software Architecture

Change failure rate is the proportion of software changes that result in a failure requiring remediation or rollback.

How it is used
Measures production stability alongside delivery-speed metrics to diagnose architecture under operational pressure.
How deep it goes
Defines the rate as deployments degrading production and requiring intervention, then links high rates to poor testability.
Examples
Uses bypassed pipeline validation and the Knight Capital case to frame the business risk of skipping deployment safety.
What you can do after
Evaluate architecture by reading change failure rate alongside delivery speed and recovery time.

Read how Grokking Software Architecture explains change failure rate →

Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform

Change failure rate is the proportion of deployments or changes that require remediation, rollback, or other corrective action because they fail.

How it is used
Uses change failure rate to expose operational risk created by manual infrastructure configuration.
How deep it goes
Defines the metric and explains causes and mitigations, but does not provide a calculation method or reporting procedure.
Examples
Uses delayed database provisioning, routing and firewall tickets, and unaudited firewall changes as operational examples.
What you can do after
Apply it via infrastructure as code, automation, and testing to reduce failed changes and remediation effort.

Read how Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform explains change failure rate →

Also covered in

What to know first

Related concepts

Questions about change failure rate

What is change failure rate?

Change failure rate is the proportion of deployed software changes that cause failures requiring remediation, rollback, recovery, or other corrective action.

Which Manning books explain change failure rate?

Build High Value Software Systems, Effective Platform Engineering, Platform Engineering on Kubernetes, Grokking Software Architecture and Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform.

What should I know before learning change failure rate?

Manning books that teach change failure rate usually introduce deployment pipeline, mean time to resolution and code coverage first.

What is change failure rate part of?

Change failure rate is part of DORA. DORA is a research and measurement framework for software delivery performance, commonly using deployment frequency, lead time for changes, change failure rate, and time to restore service.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.