Skip to main content

Do you split defects the way you might split user stories?

Last post 01:45 pm October 24, 2012 by Don McGreal
1 reply
11:42 am October 24, 2012

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?


01:45 pm October 24, 2012

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


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. For privacy concerns, we cannot allow you to post email addresses. 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.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.