Now the sprint is finished and we are stuck with a bad velocity value. We have corrected the story points for the issues at stake but we would like to be able to correct the value used in the SPRINT Report. How can we do that?
I'm not aware of a solution to this. I think it comes down to ensuring the sanity of the numbers at Sprint Start. Those are the numbers that get locked-in and contribute to the total estimated velocity for that sprint. So committing to 999x3 just shouldn't occur in the first place.
How did you go in the end? I'm guess that sprint report just continues to look weird and is marked as learning experience?
Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot