Looking for general information/best practices on managing Bug issues within a sprint. I don't think we are interested in estimating (planning poker) bugs, nor are bugs really mean for the planning board. But we definitely need to be able to include reported bugs within a sprint. What is the best way to handle this?
Well, if you think the team has the capacity to fix the bug in a running sprint, go ahead and add iti into the sprint. It will be marked as scope change. If not, you should plan your next sprint and include that into that sprint. The rest of the sprint will then be executed when you think your team can deliever it.
We always try to include QA/Testing in our estimates and therefore try to have time in our stories for bug fixes built in. This way I would create a bug, add it to the sprint and assign it and associate it with the original issue if it is deemed necessary to fix before releasing your sprint, otherwise it could be worked on in a future sprint.
Hey Everyone! Unfortunately, the venue that was hosting us on the 23rd has pulled out so we're looking for a new venue. If anyone would have a room free that we could use on the ev...
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