nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sprint Review Assistant

Neha Manchanda_i9c73q

Is there an agent or set of prompts that we can use to analyze sprint completion rates along with committed and completed story points, identify issues that spilled over, and understand the root causes of those delays?

Additionally, can we apply this analysis to the last 2–3 sprints to help inform and set a more realistic velocity for upcoming sprints?

Accepted answers

All comments

Nikola Perisic

Hello @Neha Manchanda

You can do this. You need to set your scenario, in this case it would be a default scenario that would look like this:

"You are a sprint review assistant that will help users to analyze sprint completion rates along with committed and completed story points, identify issues that spilled over, and understand the root causes of those delays. Emphasize on giving concise answers and giving answers in a bullet point format. Avoid beating around the bush and giving vague unrelated answers."

Always include that the assistant needs to emphasize on and what it needs to avoid.

Some of the tests that were made:

General sprint analysis

Breakdown by every sprint

Analysis of 3 last sprints

Peter_DevSamurai

Hi @Neha Manchanda ,

You can create your own custom rovo agent:

Rovo > Agents > Create agent.
Then name as: Sprint Review Assistant.
Prompt:
"You are a sprint analyst. For the last [N] sprints: Calculate completion rate (completed/committed points), list spillovers with root causes from descriptions/comments, and suggest velocity for next sprint based on trends."
Skills: Add "Read Jira issues" and "Generate report".
Then test in your own board -> Browse agents: Sprint Review Assistant.

I hope everything works out well for you!

Best regards,

Peter

Ollie Guan

Hi @Neha Manchanda ,

Based on the official description, Sprint Reviewer Pro can cover most of the basic “sprint review / retrospective assistant” needs you mentioned in that community post, but there are also some limitations.

https://marketplace.atlassian.com/apps/1233252/sprint-reviewer-pro-automate-sprint-reports-data-insights?hosting=cloud&tab=overview

What this app can do (highly relevant to your needs)

Sprint completion & velocity analysis
- It provides a Sprint Velocity Chart (last 8 completed sprints):
  - This is the key metric you need to estimate a realistic “story points range” for future sprints.
- You can view details for the last 50 sprints:
  - Including: sprint goals, planned/actual start and end times.
- This is sufficient to:
  - Analyze completion-rate trends of recent sprints
  - Roughly derive a velocity range for planning upcoming sprints.
Assignee-level sprint breakdown
- It has “Sprint Breakdown by Assignee”:
  - Shows per assignee: number of issues, story points, time spent.
- This helps sprint reviews/retrospectives when you discuss:
  - Whether work is concentrated on a few people
  - Whether some people are consistently over- or under-loaded.
Multi-sprint overview & export
- You can monitor up to 50 sprints per board.
- It supports CSV export:
  - This lets you use Excel / BI tools for more advanced analysis (for example: root cause classification, historical comparisons, custom team reports).

Alexey Pavlenko _App Developer_

@Neha Manchanda ,

Unfortunately, for this specific use case, there is no magic AI solution from my standpoint. In order for AI to make the right conclusions, the retrospective needs to be conducted by a team. With this in mind, I developed the app Multi-team Scrum Metrics & Retrospectives to analyze and answer exactly the questions you outlined. With it, you can get:

sprint completion rates = Completed % out of Final Scope
committed and completed story points = Final Scope and Completed Scope
identify issues that spilled over = Uncompleted Scope
understand the root causes of those delays = quantifiable in-place retrospectives

Analysis of 1 period:

Average of metrics for the selected periods:

Quantifable retrospectives:

New Project (12).png

Best regards,
Alexey

Neha Manchanda_i9c73q

Hi Peter,

Thanks for the response. Since it was a simple approach , I am trying to create this agent. However , when I try to add skills , I cannot see the skills "Read Jira issues" and "Generate report"

Can you help share the exact name?

Also , I am using standard version of JIRA so wanted to check if these skills are available in the standard version or not.

Thanks

Iryna Komarnitska_SaaSJet_

Hi @Neha Manchanda ,

If you’re looking for a practical way to do this inside Jira (without building a whole prompt/agent workflow), you might want to try the Sprint Report in the “Time in Status” app — full disclosure: it was developed by my team at SaaSJet.

It’s designed for exactly the kind of sprint analysis you described:

Committed vs. Completed (Story Points / Work Item Count / Original Time — you pick the method your board uses)
Completion rate (and when it exceeds 100% because more was delivered than initially committed)
Carryover / spillover visibility (what wasn’t finished and moved into the next sprint)
Scope changes (added vs removed mid-sprint — a common “hidden” reason velocity looks unstable)
Workload by assignee (committed/added/removed per person)
Status time + flagged items + logged time (helpful signals for “root cause” conversations: long time stuck in a status, too much WIP, blocked work, late testing/review, etc.)
Team Velocity across recent sprints (the report shows committed/completed for the last several sprints and includes an average velocity, which is useful for calibrating future commitments)

How this maps to your questions:

Analyze completion rates + committed vs completed story points → Velocity + Completion Rate sections
Identify spillover issues → Carryover metric (available after sprint is completed)
Understand root causes of delays → Look at Status Time patterns, Flagged work, Scope Change, and Workload distribution (these usually explain why items didn’t land)
Apply across the last 2–3 sprints to set a realistic velocity → Use the velocity trend + average completed work (and sanity-check against scope churn)

Where to find it (once installed): Board → More (top right) → Sprint Report.
Also nice: it supports active sprints too (shows a burndown + real-time progress), then switches to full carryover/velocity context once the sprint is closed.

TIS 130 (1).png

If your goal is “agent-like” insights, this report is often a good first step because it gives consistent sprint-by-sprint data the team can review in minutes — and you can still layer AI prompts on top later if you want narrative summaries.

Yong Yang

Thanks for recommeding Sprint Reviewer Pro App, which has a Rovo Agent to analyze the sprint health during the life cycle of a sprint. Please see

[Rovo Agent] How Scrum Teams Can Get a Clearer View of Sprint Health in Jira? for more details. This app is Run on Atlassian (safe & practical).

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

rovo