Escaped Defects Rate: Measuring What Slips to Production
Escaped Defects Rate is your quality report card from users, measuring the percentage of total bugs that your internal testing missed. Teams use it to gauge QA effectiveness. The footgun is using it to blame individuals, which just encourages hiding bugs.
The mental model
Think of Escaped Defects Rate, also called Defect Leakage, as the bugs that got away. It measures the percentage of total defects that your team's internal testing and quality assurance processes failed to catch, which were then discovered by actual users in the production environment. It's a direct measure of how effective your quality gate is before shipping.
How it works
The rate is calculated with a simple formula: (Number of defects found by users after release) divided by (Total number of defects found both before and after release). For example, if your team found 40 bugs during a sprint's testing phase and users later reported 10 more bugs in production, the total number of defects for that work is 50. The Escaped Defects Rate would be 10 / 50, or 20%. A lower percentage is always better.
When to use it
This metric is a powerful diagnostic tool for team process improvement. Use it during sprint retrospectives to spark conversations about quality. A consistently high or rising rate is a signal to investigate the root cause. It can help a team justify investing more time in activities like writing automated tests, refining the Definition of Done to be stricter, or improving peer review practices. It provides objective data to guide quality-focused decisions.
When not to use it
Never use this metric to evaluate or punish individual engineers or QA testers. Doing so creates perverse incentives, encouraging people to hide bugs or argue about whether a report is 'really' a bug, which corrupts the data and destroys trust. It's a system-level metric, not a personal performance review tool. Also, avoid comparing the rates of different teams without deep context, as project complexity can vary wildly.
One canonical example
A Scrum team completes a new feature for their e-commerce site. During the sprint, their internal QA process identifies and fixes 18 bugs. The feature is released. Over the next month, customer support logs 2 new, valid bugs related to the feature that were reported by users. The total number of defects is 18 (internal) + 2 (external) = 20. The Escaped Defects Rate is 2 / 20 = 10%. The team discusses this 10% rate in their next retrospective.
Interview question
What is the primary purpose of calculating the Escaped Defects Rate?
- a.To quantify the total number of bugs introduced by a development team in a sprint.
- b.To compare the overall quality of different software products developed by an organization.
- c.To measure the effectiveness of the internal quality assurance processes.Correct
- d.To evaluate the individual performance of quality assurance engineers.
Why? this is the answer
The Escaped Defects Rate is explicitly defined as a direct measure of how effective a team's internal quality assurance processes are. It is specifically stated that this metric should never be used to evaluate individual performance, making that option incorrect.
Just read this? Test yourself on what you have been reading.
Read the original → whatisscrum.org
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles