Why does the release burndown and velocity chart show different "completed" values per sprints?
Velocity Chart (Sprint 23) = 58.5 sp completed.
Release Burn Down (Sprint 23) = 71 sp completed.
This is making it difficult to determine which reported velocity is the "real" velocity.
Any insight would be greatly appreciated!
The velocity can be estimated as the average, over several recent sprints, of the sum of the estimates for the amount of work completed by a team per sprint — so in the chart above, the velocity = (37 + 47 + 50 +57) / 4 = 48. A team's recent velocity can be useful in helping to predict how much work can be completed by the team in a future sprint.
Thanks Michal for replying.
I'm still confused as to why the Release Burn Down, for the same team and same sprint, is reporting different numbers.
In the release burn down, it's reporting 71 sp as completed for sprint 23.
In the velocity chart, it's reporting 58.5 sp as completed for sprint 23.
If both charts are reporting different 'completed' numbers, then both charts are reporting different velocities.
I'd just like to know which report I should rely on for accurate data.
Try the Great Gadgets add-on (see https://marketplace.atlassian.com/plugins/com.stonikbyte.great.gadgets.plugin/cloud/overview). It offer simple charts for both release burndown/burnup and team velocity.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
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