How does Jira calculate average velocity for the Version Report

[Jonathan Clark]

Hi, 

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?

Thanks,

Jonathan

[Mykenna Cepek]

From the docs:

Predicted sprints

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.

More here:

https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-release-burndown-report/

[Jonathan Clark]

Thank you for the reply.  I'm pretty sure that's for the burndown report.  I can very easily tell it is not using the last three sprints to calculate average velocity on the version report.  The release burndown report on the other hand does calculate velocity in that way.

[Mykenna Cepek]

Ah yes. I'm sure you've read the docs about the Version Report by now:

https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-version-report/

Some things to confirm as you validate what it's showing you:

• Are you excluding Sub-tasks in your numbers?
• Are you also excluding archived eleases/versions?
• Does your board spread StatusCategory=ToDo issues beyond the left-most column?
• Does your board spread StatusCategory=Done issues beyond the right-most column?
• Do all the versions/releases have Start Dates?

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.

[Jonathan Clark]

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.

Thanks again,

Jonathan

[Danut M _StonikByte_]

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:

• How to track multi-team or scaled-agile projects (such as SAFe®) in Jira with Great Gadgets app 
• 7 gadgets for a powerful Scrum dashboard in Jira 

 I hope this helps. If you have any questions, please don't hesitate to contact us at support@stonikbyte.com.

Thank you,

Danut Manda

[Jonathan Clark]

Thank you!  This looks very helpful.  I will check it out.