Loading ...
Sorry, an error occurred while loading the content.

38310Re: [scrumdevelopment] Best Practices on Defect Management

Expand Messages
  • ron jeffries
    May 4, 2009
    • 0 Attachment
      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.



      -----Original Message-----
      From: "Brent Walker" <brent.walker@...>
      Sent 5/4/2009 10:42:24 AM
      To: scrumdevelopment@yahoogroups.com
      Subject: [scrumdevelopment] Best Practices on Defect Management

      I would like to see some discussions around various best practices for managing defects especially around multi-product teams (i.e. inter-related products from different teams)?
      1) Do you reduce your capacity for your team members and set that time aside for working defects
      a) These defects are preventing other teams from completing their sprint (a blocker of sort)
      2) Do you plan your sprint to include a set amount of defects for the iteration
      3) What level of flexibility does your team plan for in managing defects?
      I work with infrastructure teams and struggle to find a balance between the sprint contract and the flexibility needed to fix blocking defects requried by the consumers of the infrastructure.
      Here is an example:
      Application Team "A" has identified several defects that my infrastructure team needs to provide fixes for but are not currently preventing any stories in their current iteration.  They just want them fixed prior to their "hardening" phase of their release.
      Application Team "B" has a story in their current iteration that is unable to be completed due to a defect the infrastructure team needs to fix.
      Iteration Planning for Infrastructure Team: Planned to fix a few of Team "A's" defects but did not plan for the one defect from Team "B".  Based on the planning contract/comittment we push the defect from Team "B" into the backlog and say sorry?  We will add it to our next iteration?
      Again, looking for best practices from the perspective of an infrastructure team.
      thanks,
      Brent
      ------------------------------------
      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:
      http://groups.yahoo.com/group/scrumdevelopment/
      <*> Your email settings:
      Individual Email | Traditional
      <*> To change settings online go to:
      http://groups.yahoo.com/group/scrumdevelopment/join
      (Yahoo! ID required)
      <*> To change settings via email:
      mailto:scrumdevelopment-digest@yahoogroups.com
      mailto:scrumdevelopment-fullfeatured@yahoogroups.com
      <*> To unsubscribe from this group, send an email to:
      scrumdevelopment-unsubscribe@yahoogroups.com
      <*> Your use of Yahoo! Groups is subject to:
      http://docs.yahoo.com/info/terms/
      
    • Show all 10 messages in this topic