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)?
To have a consistent prediction in the Version Report it is important to:
Other bits and pieces may influence. This article should help figuring out if still something is missing.
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, 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.
@Jack Graves [AC] first caught our eye with his incredible breakdown of what, in his opinion, can make or break a Jira software implementation. (Read his thoughts on this thread)! In this follow...
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