What is an "escaped defect"?

The correct answer is A. A defect that was found by the customer. An escaped defect is a defect that "escaped" the development and testing process and was discovered by the customer in production - making option A correct. Option B describes an undone item or carry-over, which is a backlog/sprint planning concept, not a defect classification…

Scrum Developer Role

Question

Options

AA defect that was found by the customer.
BA defect that was planned to be fixed, but not fixed in a Sprint.
CA defect the Continuous Integration System failed to catch.

How the community answered

(32 responses)

A
91% (29)
B
6% (2)
C
3% (1)

Explanation

An escaped defect is a defect that "escaped" the development and testing process and was discovered by the customer in production - making option A correct. Option B describes an undone item or carry-over, which is a backlog/sprint planning concept, not a defect classification. Option C might sound plausible, but a defect caught by CI never reached the customer - it was caught, not escaped; an escaped defect by definition slipped past all internal safeguards.

Memory tip: Think of the word escape literally - the bug broke out of your safety net (testing, CI, QA) and ran free into the wild (the customer's hands). If it was caught internally, it didn't escape.

Topics

#escaped defect#quality#customer-found defect#testing

Community Discussion

No community discussion yet for this question.

Full ASF Practice