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?
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :). In the spirit of this month's august-challenge, we're sourcing stories of Jira Service Desk activation fro...
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