I'm trying to understand our velocity chart but am having a hard time understanding how commitment works.
In a few of these sprints we have had work rollover into the next one - a issue I'm trying to solve / provide more clarity using our velocity chart.
Using our sprint 'Zeus' as an example, how is it calculated as 1 commitment? A large majority of this work did in-fact rollover. Do those points not count?
Greatly appreciate the help to better understand this report!
Commitments in a velocity report are only being calculated at the moment that specific sprint starts. When that sprint starts, all the estimates of issues in that sprint are going to be the grey bar (commitments). The green bar is the total completed estimates when the sprint ends.
Issues added to a sprint after it starts, or changes to estimations after the sprint starts are not calculated into the commitment of that sprint. There are more details about this report in Velocity Chart. Another common pitfall of reading this chart can be in regards to the use of subtasks:
NOTE: Estimates from sub-tasks are not included in the Velocity Chart's calculation. (Only estimates from parent tasks are included.)
Does this help explain what you are seeing here?
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events