Sprint Spillovers - without using Sprint report

[Sarthak Solutions]

Is there way to view sprint spillovers without referring to Sprint report ? I am trying to generate an automated Sprint report Dashboard/View which needs this important information to reflect.

[Bill Sheboy]

Hi @Sarthak Solutions -- Welcome to the Atlassian Community!

In my experience...

Work item carry-over from one sprint to the next is a symptom of some root cause.  Those could include challenges with backlog refinement, sprint planning, team focus, product / code quality, people-incentive policies, etc.  Hopefully, such carry-over is infrequent.  Rather than building reporting for this, I recommend using the existing Sprint Report and discussing this with the team in a Retrospective to identify the root cause, and then design experiments to improve team processes to eliminate the problem.  If carry-over reporting is created without the team discussion, this could lead to normalizing carry-over, or other unintended consequences, reducing the chance the root cause will be addressed.

If the team decides they still want to build automated reporting to track carry-over, they could:

• Investigate marketplace apps / addons to do this
• Use automation rules to detect the condition, adding indicators to the impacted issues.  Then with the built-in features of JQL, report on the issues in the List View or in a Dashboard gadget.

Kind regards,
Bill

[Valeriia_Havrylenko_SaaSJet]

Hi @Sarthak Solutions  👋
Welcome to the Community! 

If you're open to apps, Sprint Report from Time in Status can be a great solution.

How Time in Status Sprint Report Can Help:

• Multi-Sprint Analysis – View trends over the past 7 sprints to identify peaks and valleys in workload.
• Tracks time spent in each status during the sprint
• Highlights issues that were not completed and carried over
• Provides data exports & visualizations for deeper analysis
• Historical Data Tracking – Helps correlate trends with infrastructure-related obsolescence work.
  
  

Add-on developed by my team. 

I hope you find this helpful 🚀

[Ilze Leite-Apine - eazyBI]

Hi

I am Ilze from eazyBI reports and charts app, Jira Marketplace app for data analytics.

eazyBI has a wide set of Sprint scope change metrics to use in reports. I imagine two approaches how to look at sprint spillovers.

1. You may want to see not completed story points (or issues) at the end of each sprint, using measures "Sprint story points not completed"/ "Sprint issues not completed" that calculate issues not yet moved to Done statuses at the sprint completion moment. The report, showing all board sprints with spillover issues, could look the following:

From there, you can drill across particular issues, their statuses, etc.

Also, you can visualize it as a chart, add trends. etc.

2. Another approach, if you need to see how many issues/story points included in the selected sprint are spillovers from previous sprints, is a custom calculation, the example from our demo account. The "Stories rolled from previous sprints" shows exactly that—the sum of story points that were not completed in previous sprints and now are added in the sprint you are interested in.

Probably, you have your report (or set of reports) in mind, and I am certain it can be achieved in a similar way as my approaches. Let me know, and I will create an example report on that. 

Best regards, 

Ilze

[Danut M _StonikByte_]

Hi @Sarthak Solutions,

Welcome to Atlassian Community!

Jira does not have gadget able to show this info. Also, I see no ways at the JQL/filtering level for determining the sprint spillovers.

If you consider using a plugin from Atlassian Marketplace, a good alternative to the Jira's Sprint Report could be the Sprint Burndown Burnup Chart gadget offered by our Great Gadgets app. Beside the chart, this gadget can display a Data tab showing a sprint report similar to the one of Jira, which can be easily exported in CSV format.

It offers an Issue Not Completed section, showing the issues moved to next sprints.

Same app offers also a Team Velocity gadget with the work committed, completed, scope change, added, removed, etc for past sprints. It also offers a Data tab with details about each sprint.

Hope this helps.

Danut

[Alexey Pavlenko _App Developer_]

Hi @Sarthak Solutions ,

There are no native JIRA gadgets, unfortunately, that can reflect the same information as the Sprint Report. You can use the app I developed for that - Multi-team Scrum Metrics & Retrospective.

With it, you can display Uncompleted Scope or any other custom JQL metric for multiple boards/teams across sprints, months, quarters, half-years, or years in a single view. Also, you can do in-place retrospectives and much more.

Best regards,
Alexey