Re: [scrumdevelopment] Sprint planning with defects/bugs
Handle bugs like stories in order of priority. When the list of bugs are known, the planning process works the same by committing to the list of highest priority items into the Sprint Backlog. If a bug story is too complex, split them to smaller sub tasks/stories within the story. Priorities being equal with other stories with business functions, then the team, under the guidance of the PO, will need to determine how many percent of a Sprint can be allocated for bug stories. To plan a Sprint to account for new/unknown bugs, allocate an x% of the Sprint for bug stories. We have used 5% and 10% depending on the teams.
--- On Thu, 1/8/09, Christophe Boutter <c.boutter@...> wrote:
From: Christophe Boutter <c.boutter@...>
Subject: [scrumdevelopment] Sprint planning with defects/bugs
Date: Thursday, January 8, 2009, 1:43 AMWe've been doing Scrum for a while now. But in the next sprint planning
meeting we will take into account some bugs/defects for the first time.
These couldn't be fixed in the last sprint, but need to be fixed. Since
the bugs aren't that small, we don't know how to tackle the problem but
we would like to take them into account in our sprint plan.
Should we split the bug into different tasks? Or should we plan the bug
as a whole? Any other ideas?
Thx for the answers,
To Post a message, send it to: scrumdevelopment@...
To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...! Groups Links
<*> To visit your group on the web, go to:
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to: