Felix, Thanks for the response. Just to be clear, I'm talking about bugs found in production. I think fixing these bugs can be planned, just like a user story. I would think that you would want to size those bugs in order to add them to the next development sprint. Otherwise, your velocity would get skewed because you would be spending time on things not accounted for in the sprint. Just curious, how are you planning on incorporating bug #907 into your next development sprint?
Thanks, as always, Scott On Oct 12, 6:19 am, Felix Schwarz <[email protected]> wrote: > Hi Scott, > > thanks for your efforts reproducing the bug - we'll try to fix it even > though you found a workaround. > > Am 09.10.2009 21:18, schrieb Scott: > > > We found what's causing the issue. We added story points to the bug > > type. This prevented the task hours associated with the bug to not be > > tallied in the sprint view. If we remove the Story Points (rd_points) > > from the bug, the totals work again. This leads me to wonder how you > > handle bugs discovered after a release is complete? We were going to > > basically treat bugs as user stories by assigning them story points > > and adding them to a backlog. Does this make sense? > > Adding bugs to the sprint backlog definitely makes sense if you can plan > them. Why do you want to have story points for bugs? > > The Scrum way to use velocity from a PO perspective is to plan you > releases (how much user functionality/new features the team can do in a > number of sprints). While bugs have value, you can not plan them so they > should not influence the team's velocity. > > fs > > smime.p7s > 4KViewDownload --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH http://www.agile42.com and is focused in supporting Agilo for Scrum users. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo?hl=en -~----------~----~----~----~------~----~------~--~---
