Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


On sprint end, the velocity chart shows incorrect number of story points on the committed bar. Why?

Sprint 16 ended, burndown chart gives a picture that we started with 162 story points(which is the true case). Sprint report also says the same story. However in velocity chart, the committed bar on Sprint 16 says 214 story points as opposed to 162. Why is there a discrepancy? Let me know if I am missing anything here.



2 answers

I have the same problem!

Since a few sprints now we have too high committed numbers in our velocity charts.

Example Sprint 59

Velocity: Committed = 68

Sprint Report: SP at start of sprint 42 = 27 + 20 - 5

  • Completed Issues: Story Points (27 → 30)
  • Issues Not Completed: Story Points (20 → 18)
  • Issues Removed From Sprint: Story Points (5)

I wonder why the 5 SP from the removes do not count for the start of the Sprint but this at least adds up. But we have no idea where the 68 are supposed to come from. 


Example Sprint 58

Velocity committed 58 vs. 32 in Sprint Report (which is what we actually had in planning)


Any idea what is causing this?

 We use Jira v9.4.5



Sprint Report.pngVelocity Chart.png

I am seeing the same thing on our board - the burndown chart starts from 36, while the velocity chart's Committed column is at 43, for the same sprint.


I'm noticing similar problems in other sprints as well - the Completed value is correct and matches with what we are seeing in the burndown chart, while the Committed value is constantly not matching (being higher) the burndown chart.

Suggest an answer

Log in or Sign up to answer