Often times in a sprint, we get tickets that are underestimated. In other words, the logged hours will exceed the original estimate. This is what is indicated as estimate accuracy in Agile's chart board.
The great thing is, during the sprint if we see the yellow line goes up we know that the estimate has been under. But the question is, how do you find where all that times has gone to? How do you get a list of tickets of where the extra time went into at the end of the spring for review purposes?
Use a Scripted Field from Jamie's Script Runner Plugin, and return the difference between time spent [using the function
getTimeSpent()] and orginal estimate. Publish a filter using the Sprint version sorted by this new custom field in descending order. The top ones are the ones to be checked during your retrospective meetings to understand the quality of estimation.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
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