Defects are an unavoidable part of software development. No one is perfect and no methodology is foolproof; as a result, every Scrum Team will deal with defects at some time during product development. Scrum provides plenty of opportunities for inspection and adaptation, thereby helping to take steps to minimize the occurrence and impact of defects. The way we deal with defects in Scrum depends largely on when the defects are discovered:
- In-Sprint defects are defects discovered within the current Sprint.
- Out-of-Sprint defects are discovered in previously released increments.
Before delving into these two scenarios, let's talk a bit more about defects.
Knowing how to triage defects
A defect is a discrepancy between the software's actual and expected behavior. A defect is usually caused by a coding or design error (a bug) or by a misunderstanding of the user requirements. When the Scrum Team becomes aware of a defect, they should ensure...