Forums

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. If you have left the first and last name fields blank on your member profile, your email address will be displayed instead.

All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

What to do with a commited PBI
Last Post 11 Mar 2013 08:10 PM by Susanta Kar. 5 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Randy Ho
New Member
New Member
Posts:47
Randy Ho

--
07 Mar 2013 07:53 AM
    There is a bug that we commited to for the sprint. Upon working the bug, it was discovered that the issue was due to system misconfiguration on the customer side and that no software changes were needed.

    We have logged that in working with the person who reported it, found that the system was misconfigured and that no further action was needed.

    We are also coming up with a plan to better verify bugs before they are accepted by the PO into the product backlog.

    We will tell the PO during the review that the PBI is done becuase the bug doesnt exist.

    Is this how we should do things? Should we approach the PO ahead of time and have the PBI removed from the sprint immediately instead?
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1685
    Ian Mitchell

    --
    07 Mar 2013 10:23 AM
    Hi Randy

    Tell the PO now. The defect you accepted into the sprint can *potentially* be traded out and other more valuable work brought in. Any work brought in should be roughly equivalent in size to the defect minus whatever effort you put into chasing it.
    Sanjay Saini
    Basic Member
    Basic Member
    Posts:156
    Sanjay Saini

    --
    07 Mar 2013 01:23 PM
    I agree
    Randy Ho
    New Member
    New Member
    Posts:47
    Randy Ho

    --
    07 Mar 2013 03:53 PM
    Thanks guys!
    Ravi Vajaria
    New Member
    New Member
    Posts:10
    Ravi Vajaria

    --
    11 Mar 2013 03:28 PM
    Another opinion. to Ian's point that the work *potentially* be traded out and other more valuable work brought in... any and all other committed PBIs should be addressed and completed before accepting new work. One or more committed PBI might take more time than expected. If fact, we are very much opposing to take any new PBI at all. Any time available after all PBIs are done can be wisely used by the team such as learning, knowledge sharing etc.
    Susanta Kar
    New Member
    New Member
    Posts:20
    Susanta Kar

    --
    11 Mar 2013 08:10 PM
    I agree Ravi to an extent.

    Taking PBI (not changing the sprint goal) would be based on team's conformance and provided there is such PBI that could be taken up & finished within the sprint. This definitely should be once the forecasted(not committed) PBIs are all done for the sprint. Otherwise, team may spend time on learning, training, KSS etc.
    You are not authorized to post a reply.


    Feedback