Today I have closed the Sprint.I have tried to see burn down chart and found that it shows scope change at couple of place. After analysis we found that if we log any defect while testing of user story it shows as scope change. In reality it is not scope change, it is part of user story. As per our DOD, testing/defect fixing should be complete within sprint.
Please let me know if you have any guideline for handling the defect of user story in active sprint.
But after starting a sprint you can not add/delete issue in starting sprint.
You can create sub-task within the story.
Here in my case:
In active sprint there is 3 stories with story points
In that stories I have created sub-task for developer.QA team will test & find 2-3 defect for the story then they will create defect in active story.As per our DOD, testing/defect fixing should be complete within sprint
I think that if those defects are found before the Demo has been accepted (and the Story is 'Done'), you can just communicate internally using comments on the ticket - it is not necessarily scope change but part of developing the story. Depending on your workflow for the story, you might want to "pull it back" a transition or two.
If the defect is identified after Demo has been accepted, however, I agree with Nic that a Defect should be created and it is scope change.
Very true, to avoid this, you could "pad" your stories while estimating them before pulling them into a sprint. Have a look at the previous stats for how much you added into the sprint as a result of adding the new defects into it and then increase your story estimates by the amount. Then you won't need to add to the sprint.
Thanks for the advice.
I have one query on this,Please let me know how to handle the defect once it is created for user story in active sprint?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs