A particular sprint's Velocity Chart Report shows 41 story points committed and 29 story points completed. When I create a report in EazyBI, EazyBI shows 31 story points committed and 26 story points resolved. Can anyone offer some guidance on how I can track down the discrepancy?
Hi Ryan again,
Measure "Story Points resolved" is not directly related to "Sprint Story points commited" measure. "Story Points resolved" shows the total number of story points of the resolved issues, in the report context. It means, if you have selected a particular project in the report, then SP from the resolved issues of this project will be calculated.
Also, if you have selected Sprint in the report, then SP from the resolved issues which are added to the sprint, will be calculated. If some issue was added to the sprint previously, but now is added to another sprint, then story points from this issue would not be included in the result.
As, usually, resolved issues are not moved from the sprint, Story points resolved could be used to count resolved story points of the sprint.
To get the number of all planned Sprint Story points (not only on the first day of the sprint), you can combine measures Sprint Story points commited, Sprint Story points added and Sprint story points removed.
P.S. A small correction to my previous answer - "Sprint Story points commited" shows total of SP which are added to the sprint until (not during) the end of the first day of the sprint.
Ilze / firstname.lastname@example.org
in eazyBI, "Sprint Story points committed" measure counts all story points (both resolved and unresolved) at the end of the first day of the sprint; if Story points are added or removed later, they are not affecting a number of committed story points. Read here about Agile measures in eazyBI.
You can click on the committed SP value and drill through issues to see a list of issues which were added to the sprint on the first day, and their story points. If there are some issues missing please write to email@example.com for more detailed assistance.
Ilze / firstname.lastname@example.org
Thank you. When I drill through the issue I see exactly as you describe–the issues that were added on the first day of the sprint.
A couple follow-up questions:
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot