Sprint Status - Planned Vs Actual and Automation Report

[Suriya Kumar Sivasubramania]

I am looking to generate a detailed sprint status report that outlines the work initially planned at the beginning of the sprint versus what was actually completed by the end. This report is crucial for assessing the team's delivery performance and identifying any gaps or areas for improvement. Ideally, I would like this report to be automatically generated from Jira for each sprint, ensuring consistency and saving time on manual reporting

[Alexey Pavlenko _App Developer_]

Hi @Suriya Kumar Sivasubramania ,

For comparing Initial Scope vs Completed Scope you can use the Velocity Report, it automatically shows the last 12 sprints. You don't need to update anything manually to see a new sprint in this report. For retrospectives, you can use standard techniques with or without Confluence page.

Another option for you is the app I developed with a strong focus on performance measurement, improvement and in-place retrospectives (no need for Confluence pages or manual efforts) - Multi-team Metrics & Retrospective. There is a specific article for this - Quantify your retrospectives to unleash the full power (the most liked article for the last 4.5 months), do recommend reading it.

Standard view:

Metrics Summary:

In-place retrospectives:

Top reasons why you fail metric or another:

Best regards,
Alexey

[Iryna Menzheha_SaaSJet]

Hi @Suriya Kumar Sivasubramania 👋
Welcome to the Community!

You're on the right track — having a consistent Sprint Status: Planned vs Actual report is one of the best ways to evaluate sprint health, team performance, and uncover improvement areas. Here's how you can approach this using Jira's built-in features and advanced reporting through apps:

1. Built-in Jira Options (Standard & Premium)

🧰 Velocity Chart (Out of the box)

• Found under Reports on your Scrum board.

• Compares committed story points (planned) vs completed.

• Limitations: Only shows story points (or issue count), no breakdown of specific stories/tasks.

📄 Sprint Report

• Lists all completed and incomplete issues.

• You can use this for post-sprint reviews but it requires manual comparison if you want structured “Planned vs Actual” metrics per sprint.

2. Automate the Report with Time in Status 

If you want an automated, per-sprint breakdown of what was planned vs completed (and more), check out Time in Status:

📊 What the TIS Sprint Status Report Can Do:

• Compares issues present at the sprint start vs those completed by end.

• Highlights gaps (e.g., scope creep, incomplete tasks, spillovers).

• Breaks data down by assignee, issue type, or status.

• Tracks time each issue spent in each status (useful for bottleneck analysis).

App developed by my team. 

If you're open to exploring Time in Status, happy to guide you through setting up your first sprint report!

[Eduardo Anflor - MindPro]

Hi, @Suriya Kumar Sivasubramania 

Welcome to the community!

Usually, the out-of-the-box Sprint Report shows the sprint's progress, plus story points added/removed during the process. However, it does not offer a good level of visibility to all team members. If you are open to a marketplace solution, I recommend Mindpro Insights. I work at Mindpro and I believe it can help you with your use case. The app allows you to create agile dashboards easily (from a template or a blank screen) and share them with internal users or external users via the customer portal.

The gadgets are interactive, if you click on one segment, the dashboard adapts to your filter. Using your scenario as an example, I created a dashboard that uses the board filter and the "Sprint Progress" gadget, so you can check the progress of all sprints in your board. You can also use the "Sprint Filter" to select just one sprint to show:

There are over 50+ gadgets you can select from, including custom gadgets (which can also be added to Jira standard dashboards).

I hope that helps.

Regards,

Eduardo

[Kate C_]

Hi @Eduardo Anflor - MindPro, when you're part of a Marketplace App team, we kindly ask that you also include text in your comment stating you work for the company that built the app, per our Partner Rules of Engagement. Thanks!

[Eduardo Anflor - MindPro]

Done

[Trudy Claspill]

Hello @Suriya Kumar Sivasubramania 

Welcome to the Atlassian community.

What do you want included in the report? Are you looking for a list of issues, a sum of story point, ...?

Automation Rules include triggers for Sprint Started and Sprint Completed, so you could automate collection of data based on those events.

https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Sprint-created--started--or-completed

In each case you have to specify the board in which the sprint exists, so you would have to have multiple rules if you have multiple boards.

If your boards contain data for multiple projects, you would also need to set the Project Scope of the rule(s) to the appropriate projects or to Global. Global and multiple-project scoped rules can be created only by Jira Administrators.

You might also want to consider looking for third party apps that would enable you to get the reports more easily and at any time.