38327Re: [scrumdevelopment] Re: Best Practices on Defect Management
- May 5, 2009Hi Brent
I'd rather agree with Spent. Blocking defects are symptoms of something else, probably technical debt.
You probably need to attack the root (definition of done? tests?) instead of the symptoms, and to set your team again in a sustainable pace. This might mean to slow down a lot, but that's the way to repay the accumulated debt and to start moving again.
Alberto2009/5/4 Brent Walker <brent.walker@...>
Sorry, NOT known....
--- In email@example.com, "Brent Walker" <brent.walker@...> wrote:
>> These items are known at the beginning of the sprint. My infrastructure team plans for items they know such as items already in our backlog but as application teams begin to exercise previously accepted infrastructure stories, they find defects due to the increase utilization of that piece of infrastructure. This now becomes a blocker on the Application team. My question is, "Do I know tell them, um Sorry but we did not plan for this so it will have to wait till our next iteration!". It is a blocker and will certainly now come up in our Scrum of Scrums.
> --- In firstname.lastname@example.org, "ron jeffries" <ronjeffries@> wrote:
> > Why wouldn't your Product Owner decide what to fix and schedule the fixes as part of the Sprint?Ronald E Jeffries
> > www.XProgramming.com
> > Sent from Web Mail ... something must be very wrong.
Web page; http://albertobrandolini.wikidot.com
Linkedin page: http://www.linkedin.com/in/brando
- << Previous post in topic