Are "remaining points" the same thing as points from rolled over tickets?

[Mara Julin]

Hello!

Our teams are trying to more closely monitor our velocity sprint after sprint. One piece of information that our leaders have requested is the # of points that were rolled over from the previous sprint.

How can I get at this data for different squad projects?

I know when I go into a burn-down chart, jira makes a note  of"remaining points" and in velocity reports there are "issues not completed" - could either of those values be considered what is rolled over to the next sprint (assuming that we roll everything over as common practice)?

[Mehmet A _Bloompeak_]

Hi @Mara Julin

You can get a report of sum of Story Points Done vs Not Done at the end of each sprint (before rolling over issues to the new sprint) for each of your project bu using Report - Charts and Graphs for Jira app developed by our team.

• You can create custom, flexible and colorful bar charts and table views for any data you want/need. As data source, you can choose Projects or Saved Filters or Advanced (JQL).
• You can set X axis to be any parameter like Created(month), Assignee, Sprint, Fix Versions etc.
• You can set Y axis to be any parameter like number of issues, sum of remaining estimates, average of story points etc.
• You can group your data on any field(Sprint, Status, Assignee, Component, Project etc.) you want.
• You can choose various date ranges like All Time, Last Year, Last 3 Months, Last 6 Months etc.
• You can modify existing Segments or add new segments.
• You can order the results by drag and drop.

Here is a sample report that shows sum of story points Done vs Not Done in Current Sprint by Components.

Here is our live demo dashboard where you can see and modify sample reports and play with them.

Hope it helps.

[Nic Brough -Adaptavist-]

Yes, you have it completely right, the "remaining points" on the "issues not completed" are indeed the same points that are rolled over into the next sprint.

In an off-the-shelf scrum process, your team would go into sprint planning, fire up the board and see that their next sprint has some points in it already (rolled over from the last one).  They don't really care that they have rolled over (the retrospective is where you discuss why you didn't complete the stuff you said you would do), other than it limits how much new work they will bring in.

I am not sure that "how much rolled over" is of that much use outside any one team.  If a team is regularly having roll-over stories, then they need to look at their estimates and commitment - they're committing to too much and need to reduce the amount they are pulling into a sprint.  Or improve the estimates on the issues, because they're too low and hence misrepresenting what the team can get through.

I think I want to question why your leaders are asking for this data - all it really tells them is that they are overloading teams, or the estimates are wrong!

[Mara Julin]

This is so helpful thank you!

Yes, we would only report out by team, I just will need easy visibility into all the teams since I have to make the report. 

I've made a dashboard for myself to create widgets for each team's data so I can see it all in 1 place - how can I surface the "remaining points" in a widget? Is that possible without having to manually click into each velocity report?

[Nic Brough -Adaptavist-]

Jira doesn't really have that simple "x points rolled over" reporting as you describe it, because it's not that useful.  What would your people learn from "team X tends to over-commit, but they're not improving their process"? 

It's certainly something you should look at, but an overall report on it across all your teams is only going to tell you what teams need to improve more.