nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why does "version report" projects a release date much farther in time than expected?

Andrea Caponio

I am currently tracking a version in JIRA.

The current status is that 28 story points have yet to be completed. Team average velocity should be around 29 story points per sprint, and each sprint has a duration of 2 weeks. I would expect a projected end date of ~2 weeks, but I see that the version reports indicate the versions to be ready in ~2 months from now.

Am I missing something? Is the version report taking into account something I do not see (e.g. the rate with which new issues are created in the same version)?

Accepted answers

Andrea Caponio

To have a consistent prediction in the Version Report it is important to:

Make sure that the Version start date is correct and corresponds to when the work on the version actually started (and not to when the work was planned).
Make sure that working days of the team are correctly configured (e.g. are days off of the whole team properly taken into account?)

Other bits and pieces may influence. This article should help figuring out if still something is missing.

All comments

Jack Brickey

Without seeing the details e.g. screenshot, I can only suggest the reason is that the current velocity of getting work done. There is the theoretical value and the predicted value. Theoretical = sum of estimates and predicted considers velocity.

Andrea Caponio

I would assume that the chart is based only on story points and only stories have story points estimation: ech sub-tasks should not be considered.

Maybe I did not understand what you exactly mean, but I do not really see how the theoretical should be 4 times slower than the mean velocity.

Andrea Caponio

Here are the screenshots.

Jack Brickey

@Andrea Caponio, I agree on the surface that the prediction shouldn't be 4x. I wish I could offer more advice but w/o seeing the details I can't say for sure. I haven't used the Version report for a couple years now and recall when I first started it was confusing for me but ultimately was able to decipher the deltas between the various prediction models. I'm guessing you have already read this article but sharing just in case it helps.

Hopefully others that are actively using this report can provide some better assistance.

Andrea Caponio

To have a consistent prediction in the Version Report it is important to:

Make sure that the Version start date is correct and corresponds to when the work on the version actually started (and not to when the work was planned).
Make sure that working days of the team are correctly configured (e.g. are days off of the whole team properly taken into account?)

Other bits and pieces may influence. This article should help figuring out if still something is missing.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software

version

report