Question about JIRA version report's predicted release date

I have a question about JIRA's version report: 

According to the documentation, the predicted release date is based on the "estimated work remaining". When certain tickets have no estimation, does that mean that the prediction assumes there is no work associated with these tickets?

For example in our company not all stories are estimated right away and defects are (by design) never estimated. In order to estimate stories, we use story points.

1 answer

0 votes

Hi Christoph,

The prediction does not assume there is no work associated with the unestimated issues, but as there is no estimate, it cannot take them into account for the prediction.

There is some information that might help you interpret the accuracy of the report:

A first thing - as also mentioned in the documentation your refer to - is the optimistic and pessimistic predicted release date. The prediction adds 10% of uncertainty / deviation to your velocity metric of past work delivered to account for fluctuations in the speed of delivery.

And second, there is an indication of the percentage of unestimated issues in your backlog (shown in red in the chart). Although they aren't quantified, it gives you an indication of the work in your backlog that is not accounted for in terms of estimations. So you at least get a feel of how reliable the predicted release date might be at a given point in time.

@Walter Buggenhout [ACA IT] what would be nice is if the same chart was provided but considered cycle time and used monte carlo instead of estimates - that would be REALLY powerful.

 

Why use a 10% for pessimistic and optimistic when you can use a monte carlo simulation? The chart would look the same, it would just have a confidence band with multiple "times to complete" with a % of certainty. 

@Walter Buggenhout [ACA IT] It would make sense for the Un-estimated Issues to be given an assumed size (for charts and Sprint sizing) until actively sized.

This is essentially what happens now, just that the assumed ticket size is 0.

There just needs to be a question asked when a Project is opened:

"What size should be given to un-estimated issues (until they are estimated)?"
Options: 1,2,3,5,8,13... OR "Mean/Median/Mode of sized Issues"

Like 1 person likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Wednesday in Jira

Make your Atlassian Cloud products more secure: our NEW admin security guide

Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...

136 views 0 6
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you