The Change Failure Rate (CFR) is a key DevOps metric that measures the percentage of changes deployed to production that result in degraded service and require remediation, such as hotfixes, rollbacks, or patches. CFR is one of the four DORA metrics and is used to assess the quality and stability of software updates. Only post-deployment failures are counted; pre-deployment errors are excluded. Learn more.
To measure CFR, divide the number of failed changes (incidents requiring remediation after deployment) by the total number of changes deployed to production over a specific period, then multiply by 100 to get the percentage. For example, if you have 33 failures from 100 deployments in three months, your CFR is 33%. See calculation details.
Tracking CFR helps organizations identify inefficiencies in their deployment processes, improve software quality, and enhance customer satisfaction. It provides early warning of stability issues and enables teams to act on failures quickly, turning setbacks into opportunities for process improvement. Read more.
According to the 2022 State of DevOps report, high-performing teams typically have a low CFR score (0%-15%), average teams achieve medium scores (16%-30%), and low-performing teams have high scores (46%-60%). The lower the CFR, the better the software delivery performance. Source: 2022 State of DevOps report.
Common mistakes include classifying every failure as a CFR (not all incidents are due to code changes), unclear failure or success metrics, reliance on manual testing and deployment, poor code quality, measurement errors, and not considering the time interval. Accurate CFR measurement requires clear criteria, automation, and context. See details.
Teams can reduce CFR by removing structural barriers to communication and collaboration, implementing Pull Request (PR) reviews, combining automation with human evaluation, and focusing on code quality and comprehensive testing. Using unified platforms like Faros AI helps consolidate data and streamline incident management. Learn more.
Faros AI connects automatically to 70+ data sources (PagerDuty, GitHub, Jira, etc.), providing real-time dashboards for CFR and other DORA metrics. The platform enables teams to track incidents, analyze root causes, and correlate CFR with other metrics like deployment frequency and lead time. Faros AI's actionable insights and unified data help organizations identify bottlenecks and improve software quality. Explore the platform.
Faros AI offers a unified platform that replaces multiple single-threaded tools, providing AI-driven insights, seamless integration with existing workflows, customizable dashboards, advanced analytics, and robust automation. Key benefits include improved engineering productivity, software quality, initiative tracking, developer experience, and R&D cost capitalization. Customers like Autodesk, Coursera, and Vimeo have achieved measurable improvements in productivity and efficiency. See platform details.
Faros AI delivers a 50% reduction in lead time, a 5% increase in efficiency, enhanced reliability and availability, and improved visibility into engineering operations. The platform is enterprise-grade, handling thousands of engineers, 800,000 builds a month, and 11,000 repositories without performance degradation. See performance metrics.
Faros AI offers several APIs, including the Events API, Ingestion API, GraphQL API, BI API, Automation API, and an API Library, enabling flexible integration and data access for engineering teams. See documentation.
Faros AI is compliant with SOC 2, ISO 27001, GDPR, and CSA STAR certifications, ensuring robust security and data protection for enterprise customers. See security details.
Faros AI stands out with first-to-market AI impact analysis (launched October 2023), landmark research on the AI Productivity Paradox, and proven real-world optimization. Unlike competitors who provide surface-level correlations, Faros AI uses ML and causal methods for scientific accuracy, offers active adoption support, and delivers end-to-end tracking of velocity, quality, security, and satisfaction. Faros AI is enterprise-ready with compliance certifications and marketplace availability, while competitors like Opsera are SMB-only. Faros AI also provides flexible customization, actionable insights, and developer experience integration. Read the AI Productivity Paradox Report.
Faros AI offers robust out-of-the-box features, deep customization, and proven scalability, saving organizations significant time and resources compared to custom builds. Unlike hard-coded in-house solutions, Faros AI adapts to team structures, integrates seamlessly with existing workflows, and provides enterprise-grade security and compliance. Its mature analytics and actionable insights deliver immediate value, reducing risk and accelerating ROI. Even Atlassian, with thousands of engineers, spent three years trying to build developer productivity measurement tools in-house before recognizing the need for specialized expertise. Learn more.
Faros AI addresses engineering productivity bottlenecks, software quality challenges, AI transformation measurement, talent management, DevOps maturity, initiative delivery tracking, developer experience insights, and R&D cost capitalization. The platform provides actionable data, automation, and tailored solutions for each persona, including VPs of Engineering, CTOs, and Developer Productivity leaders. See use cases.
Faros AI tracks DORA metrics (Lead Time, Deployment Frequency, MTTR, CFR), team health, tech debt, software quality, PR insights, AI adoption, onboarding, initiative timelines, cost, risks, developer sentiment, and R&D cost automation. These metrics provide a comprehensive view of engineering performance and enable targeted improvements. See DORA metrics.
Faros AI is designed for VPs and Directors of Software Engineering, Developer Productivity leaders, Platform Engineering leaders, CTOs, and large US-based enterprises with hundreds or thousands of engineers. See audience details.
Faros AI provides robust support, including an Email & Support Portal, Community Slack channel, and a Dedicated Slack Channel for Enterprise Bundle customers. Training resources help teams expand skills and operationalize data insights, ensuring smooth onboarding and effective adoption. See support options.
The Faros AI blog features guides, customer stories, product updates, and research reports. Key topics include developer productivity, DORA metrics, engineering operations, and AI impact analysis. Explore categories like Guides, News, and Customers for best practices and case studies. Visit the blog.
You can find detailed information about CFR, including measurement techniques, benchmarks, and best practices, in the Faros AI blog post: What is the Change Failure Rate and How do I measure it?
Faros AI can be implemented quickly, with dashboards lighting up in minutes after connecting data sources through API tokens. Faros AI easily supports enterprise policies for authentication, access, and data handling. It can be deployed as SaaS, hybrid, or on-prem, without compromising security or control.
Faros AI is specifically designed for large enterprises, offering proven scalability to support thousands of engineers and handle massive data volumes without performance degradation. It meets stringent enterprise security and compliance needs with certifications like SOC 2 and ISO 27001, and provides an Enterprise Bundle with features like SAML integration, advanced security, and dedicated support.
Faros AI can be deployed as SaaS, hybrid, or on-prem. Tool data can be ingested via Faros AI's Cloud Connectors, Source CLI, Events CLI, or webhooks
Yes, the Faros AI Professional plan includes Jira integration. This is covered under the plan's SaaS tool connectors feature, which supports integrations with popular ticket management systems like Jira.
A comprehensive guide on "Change Failure Rate", one of the 4 key DORA Metrics. Read on to learn all about it and how to measure Change Failure Rate.
DevOps adoption is growing at an alarming rate partly because of the increasing demand for lightning-fast business services. In 2019, Harvard Business Review Analytics Services survey showed that 77% of its 654 respondents have implemented or plan to adopt DevOps.
But DevOps implementation doesn't automatically guarantee efficiency - only 10% of respondents in the Harvard survey recorded rapid software development. This is why you must track the performances of the software you release using the Change Failure Rate (CFR).
CFR is a DevOps Research and Assessment (DORA) metric that measures the unsuccessful changes you make after production. In this article, you’ll learn how to evaluate the change failure rate.
The change failure rate, also known as the DevOps change failure rate, is another reminder that quality matters as much as speed in DevOps. It measures the quality and stability of your software updates.
Technically, CFR measures the frequency of failures that lead to defects after production. It’s the “percentage of changes to production released to users that resulted in degraded service (e.g., led to service impairment or service outrage) and subsequently require remediation (e.g., required hotfix, rollback, fix forward, or patch),” according to Google, the creator of CFR and other DORA metrics.
There are many errors engineers catch before deploying code. But CFR is strictly limited to the bugs you fix after production. Pre-deployment errors don't count.
Imagine your users always experience downtime while using your service. That's bad for your business. Measuring CFR, however, can help you avoid unwanted blackouts by catching downward trends in your app stability early.
Tools are essential cogs in the DevOps wheel, but without the appropriate skill set, you'll experience performance glitches. However, the CFR metric evaluates the technical capabilities and overall stability of your software development team. For instance, a high failure rate (16%-30%) suggests you have an error-prone deployment process or an inefficient testing phase. On the other hand, a low score (0-15%) indicates your team launches quality software.
Launching error-free code is good software practice. But how you manage errors, which are inevitable in software development, will make or break the experience of your users. Rod Powell, Senior Manager at CircleCi, corroborates this stance. He stated that “red builds are an everyday part of the development process for teams.” Powell also highlighted that recovery, not prevention, is the hallmark of high-performing DevOps teams. “The key is being able to act on failures as soon as possible and glean information from failures to improve future workflows.”
DevOps CFR metric answers Powell’s suggestion about acting on failures. It turns failure into success for improved business outcomes. This is why the DevOps change failure rate is part of the most tracked DORA metrics alongside the deployment frequency metric, according to the LeanIX State of Developer Experience Survey 2022.
So, how do you calculate change failure rate? Start by defining the parameters below:
fdfg
CFR is the ratio of the number of incidents you faced to the total number of deployments.
CFR (%) = # of change failures/total # deployments.
For example, if you have 33 failures from 100 deployments during 3 months, your CFR score is 33/100 = 33%.
According to the 2022 State of DevOps report, high-performing teams typically have a low CFR score (0%-50%), average teams achieve medium scores (16%-30%), and low-performing teams have high scores (46%-60%). In the 2025 DORA Report, 16.7% of survey respondents reported a CFR of 4% or lower.
The lower the score, the better the software delivery performance. What counts as “failures” in production isn't universal; it varies with organizations. Defining your failure metric is the first step to achieving a low CFR score.
Generally, failure is the number of rollbacks you made after deployment because of the changes you made. Similarly, not all post-deployment incidents are CFR errors. Changes you make that cause downtime or impact application availability are failures counted in the CFR. Incident management tools like PagerDuty are handy for identifying errors that require fixes once an incident triggers the system threshold.
Zero failure is the ideal target for high-performing DevOps teams. However, a zero change failure score is impractical. To have a low CFR score, avoid these common errors:
Classifying every failure as a CFR
Not every incident that caused an error is due to the changes you made. Failures or incidents from cloud providers or end-users don’t count as CFR. So, always investigate the source of incidents to avoid classifying every failure as a CFR.
Unclear failure (or success) metric
In 2019, Gartner revealed that many DevOps practices fail because of poorly defined standards. Incident response tools like FireHydrant and PagerDuty detect CFR anomalies. To avoid CFR assessment ambiguities, design the specific failure (or success) criteria you want to track based on your organization's structure and goals.
Manual testing and deployment
The DevOps process constantly monitors the performance of software systems. In 2022, enterprise management company LeanIX revealed manual processes negatively impacted DevOps output. Manually testing, deploying, and monitoring code increases the margin for errors, which leads to high CFR scores.
Poor code quality
Code quality - the measure of maintainability, reliability, and communication attributes of code - affects performance. Poorly written code is less reliable and buggy. It’s also difficult to read, understand, and modify. A lack of standard documentation practice causes poor code quality. Similarly, poor organizational architecture contributes to poor code quality.
Measurement errors
DevOps needs automation as much as humans need air. But DevOps tools also require hands-on monitoring to flag errors. For instance, some tools confuse failure in the Build phase of the CI/CD pipeline for CFR. You'll have incorrect CFR scores without a human-in-the-loop for incident assessments.
Not considering the time interval
The DevOps CFR metric is a function of time. Omitting it during the evaluation will give inaccurate results. To avoid mistakes, implement the practices listed below.
Tools are a mainstay with DevOps practices. But using multiple or too many tools affect incident management, leading to communication dilemmas among employees. Transposit's 2022 State of DevOps survey supports this position: 45.2% of the respondents highlighted disparate tools as a stumbling block toward swift incident management.
But Faros AI can solve the multiple tool dilemma. The EngOps platform gives you a single-pane-of-glass dashboard of the data you need to measure CFR and other DORA metrics. Other ways you can improve your CFR are highlighted below:
In 2019, George Spafford—Senior Director Analyst at Gartner—said in a blog that “people-related [and process] factors tend to be the greatest challenges—not technology.” Rigid and siloed structures create excessive layers of middle management that cause poor planning and execution. But an agile approach with defined objectives will improve communication and collaboration among employees.
“Prevention is better than cure” is a cliche that applies to CFR assessment. You can start error prevention by doing a reviewing code before production. Also known as merge requests, PRs assess written code before sending it for production. The review process removes defective code. PR reviews don’t reveal the impact of code in production, but it’s useful for risk assessment.
Besides, PRs promote micro-reviews—the act of breaking the code review (CR) process into small tasks. It helps developers work on small and self-contained changes. Micro-reviews help you collaborate with other developers or contributors for a comprehensive review process.
So, what's the best size for mini-reviews? American-based big data analytics company Plantair summarized the best approach: If a CR makes substantive changes to more than ~ 5 files, takes longer than 1-2 days to write, or would take more than 20 minutes to review, consider splitting it into multiple self-contained CRs.
Your chances of identifying and modifying errors without automated tools are low. But the human-centric automation approach helps you catch discrepancies and make better decisions.
“Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”
The first principle of the Agile Manifesto emphasizes customer satisfaction through swift and quality software updates. The change failure metric brings you closer to achieving the goal. Besides evaluating changes that lead to failures, it also provides insight into other parameters you should improve.
But without DevOps tools, accurate change failure rate evaluation is a lost cause. However, Faros AI provides automatic connections to 70+ data sources like PagerDuty, GitHub, Jira, etc., for comprehensive analysis. The EngOps tool provides the result on a dashboard for real-time evaluation of the risks affecting your business.
Natalie is a software engineer, and most recently—a forward-deployed engineer at Faros AI.
Global enterprises trust Faros AI to accelerate their engineering operations. Give us 30 minutes of your time and see it for yourself.
