Handling
Bugs
My Point of
View
Within a Sprint:It is important to complete the team's acceptable level of testing during the sprint and before Sprint Review. From this, bugs from the current sprint will be need to addressed. Here is the recommended way to do so:
- If the bug is related to
an acceptance criteria not being met, fix it during the
sprint.
- If the bug is due to a gap
that was not anticipated (business gap), get with the Scrum Master/Product Owner
and discuss the bug to prioritize its resolution. This may result in the
creation of new story instead of a defect.
- If the bug is reported too
close to the Demo, evaluate the severity with the entire Scrum Team. If it is a
show-stopper then raise it as a Blocking
issue.
- If the bug is easy/quick to
fix (one liner, etc), then just fix
it.
- If the bug is not trivial,
and not a blocker, then add it to the backlog.
- If the bug is a blocker then
add a task to the current story in the current sprint to capture the work
required to fix it, and start working on it. This may require that another story
be moved from the current sprint to the backlog to account for the new hours.
(The Development Team only has so many hours available within a sprint. See:
Capacity Planning)
http://agileatlas.org/articles/item/how-to-handle-defects-in-scrum
http://www.infoq.com/news/2009/07/coping-with-bugs
http://www.mountaingoatsoftware.com/blog/should-story-points-be-assigned-to-a-bug-fixing-story
