How is sprint capacity/velocity insight calculated?

[Matt Hudson]

Hello, all. 

We are using Advanced Roadmaps for Jira v9.12.11 (Jira server v9.12.11). We have a scrum board that is the data source for an Advanced Roadmap Plan, and the team has sprints that are managed via that scrum board. As such, we are able to view the sprints across the top of the plan. 

The problem we are seeing is the calculation of capacity for each sprint. Different people can look at the same exact plan, and the number is different. I can add a filter tht should reduce the number, and it grows. Removing the filter gives it a third value.

While it is sometimes correct (particularly for future sprints that aren't fully planned), most of the time the value reported is much higher than the number of story points on the tickets that are included in the sprint. I can't seem to figure out any rational correlation to the issues (stories, bugs, tasks and epics are all we use). 

I have looked at the story points assigned at the Epic level (which we use for high-level estimation before breaking down the work into individual issues), the Target Start and End dates, the sprints that are assigned (or not assigned) and I just can't find the pattern. 

Could somebody explain how this number is calculated? 

Thanks,
Matt

P.S. Attaching a photo of the display/field I'm talking about here:

[Marc - Devoteam]

Hi @Matt Hudson 

Are their multiple teams in the plan, do they have different people set and different capacity?

is the team field used on the issues?

Also check the documentation around capacity planning; manage-capacity-in-advanced-roadmaps 

[Matt Hudson]

That link is very helpful info - thanks for sharing!

We have only one team, and the team field is set for issues that the team is going to work - we do NOT set the team field for issues that will be done by others or that are not being planned. My assumption here (which may be incorrect) is that the sprint capacity info (which is only present above the work that DOES have the team set) will only count those issues that are assigned to the team. 

That said, even if I include issues that are NOT part of the team's work, the numbers still don't seem to work out. Or rather I cannot determine how the system arrives at the number in question. Perhaps it has something to do with end dates set for epics that contain the issues? But even if that is all true, why would different people looking at the same plan have different totals?