You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.