I am currently performing my SIT testing phase - [ the non functional user story ] - as a 'Sprint' with 72 hours of effort earmarked for this user story.
Now when i add a bug to the ongoing sprint it shows up as scope change in the burndown report. In my case it is not, as i know it is easily manageable within the allowed 72 hr bandwidth I have.
I would like to if there is any way to add bugs to the ongoing sprint without getting this 'scope change' comment ?
As per my understanding 'scope change' comment is fine as long as i have bugs to resolve and it is exceeding my 72 hr bandwidth.
If anyone has done any workaround on this part, pls let me know.
Thomas Deiler is a Bavarian, Mountaineering, Senior Agile Coach. In this Showcase, you will learn about his journey from software engineer to project manager, his freelance philosophy, and much more....
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot