Working with bugs in Scrum

Mar 17, 2008 at 9:16 PM
We create a "Bugs from previous sprint" and a "Maintenance" product backlog item for every sprint. In the "Bugs from previous sprint" we add found bugs in new features and think of those as unplanned work that must be fixed to ensure that well-tested functionality pays off (or the delivery capacity of the team goes down). Bugs found in released code are created in a non-Scrum project and then imported during sprint planning into time-boxed maintenance product backlogs, if the number of bugs in released code increases we have to allocate more time for maintenance in the sprints to get more bugs fixed (which of course affects new development).

That is our current strategy for handling bugs, how are you handling bugs ?

Mar 20, 2008 at 9:53 AM
Today we handle bugs off-dashboard but from the next sprint we are implementing this feature.
Apr 1, 2008 at 2:01 PM
We are just getting ready to use scrumdashboard. Today, with the paper cards, we add a card for each bug, and treat them as there own backlog item. Part of this is that we started with a fairly large backlog of bugs. The conchango template seems to treat bugs as product backlog items as well. At least the queries do. In dashboard you can add a product backlog item like "stabilize", then add the bugs to the item for the sprint. This is effectively what perb is doing based on his/her description. This does add an extra step in getting the bugs onto the dashboard though. Each sprint you have to link the bugs you plan to address to the product backlog item in team system, or import the bugs to the product backlog item using dashboard.

I am trying to decide if this is going to be confusing or cumbersome for my team.
Apr 7, 2008 at 10:57 AM
See issues #1772 and #1838 (from Issue Tracker), Scrum Dashboard should handle both scenarios better in the next version.