The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
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.
But is this approach correct - ' anything added to the sprint once it has begun is a scope change, even if it is well achievable within my estimated efforts ' ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
See if you are adding a bug it means, you are adding it so that it can be tracked. If you do not have it be estimated, leave it as zero. As I said, it wont affect the burndown.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.