You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm trying to figure out how Jira calculates the average velocity for the version report. Dividing the number of points remaining by the number of 2 week sprints based on the projected date gives me a much lower average velocity than I get if I calculate the average velocity manually. Can someone help me understand what the data behind the version report is based on?
From the docs:
Predicted sprints are calculated based on your team's velocity* (amount of work completed in the last three sprints), and the total work remaining in your backlog. Scope change is not considered when calculating the velocity*, but is included in the total work remaining.
Ah yes. I'm sure you've read the docs about the Version Report by now:
Some things to confirm as you validate what it's showing you:
If none of the above helps your numbers line up, click the "Getting help" link at the bottom of the page linked above and raise a "support request". You're paying for Atlassian support, go ahead and use it.
For bonus points, also point them to the documentation page for this report (above) and suggest they include whatever missing information you discover. And let us know here too.
Thank you again for your help. I think the issue is that we took a break to replan due to lack of vision. Based on what I've ready, Jira uses working business day velocity, not sprint velocity for the Version report. So, I believe this means it is including all the time where we were replanning in the calculation.
Your suggestion of contacting support is a good one. I will go there.
Hi @Jonathan Clark,
As an alternative to the confusing and limited Jira reports, take a look over our our Great Gadgets app. It offers all you need to track your project releases in an efficient and effective manner.
For example, with the Release Burndown Chart gadget, you can specify how to calculate the velocity when doing the forecast of the ETA.
Take a look over the articles from our blog to make an idea:
I hope this helps. If you have any questions, please don't hesitate to contact us at firstname.lastname@example.org.