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.

Do you split defects the way you might split user stories?
Last Post 24 Oct 2012 12:45 PM by Don McGreal. 1 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Thom Gray
New Member
New Member
Posts:1
Thom Gray

--
24 Oct 2012 10:42 AM
    Your team schedules defects into your iteration backlog in the same way that it schedules user stories. During the sprint, your team spends time on the defect. But then you reach the end of the iteration and the defect is not completely fixed. What does your team then do with that defect? Do you split it in the same way you might split a user story?
    Don McGreal
    New Member
    New Member
    Posts:11
    Don McGreal

    --
    24 Oct 2012 12:45 PM
    Hello Thom,

    If that defect is not completely resolved, then it is not considered done and should go back on the Product Backlog. The team gets no partial credit, but can bring the defect in to the next Sprint to complete it (if it is still important to the Product Owner).
    However, if the Product Owner sees true value in part of the resolution, then they have the right to split it up. But ideally, that is something that should have been done when first identifying the defect or at the beginning of the Sprint.

    Don
    You are not authorized to post a reply.


    Feedback