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.
As a Belgian, beer-lover and home brewer, beer is one of my great passions. I love the fact that with just a few ingredients (usually just water, hop and malt) you can create so many different tastes...
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