📊 Sprint Metrics Suite
Retrospectives Backed by Real Jira Data
No more tab-switching or screenshotting Jira reports. SprintRetro uniquely integrates rich sprint insights directly into your retrospective board - helping your team reflect with facts, not just feelings.
From velocity and carryover to burndown and cycle time, the Sprint Metrics Panel gives you and your team a full view of what really happened during the sprint.
📍 Where to Find It
The Sprint Metrics Panel appears on the right-hand side of your retrospective board if you’ve selected a sprint during session setup. It opens by default, but can be:
Minimized by any user
Fully hidden from participants by the moderator via session settings
You can also click “View more details” to expand the panel to full screen.
🧱 Metrics Sections Breakdown
1️⃣ Sprint Goals
Team members can manually add sprint goals to this section.
Anyone in the session can add, edit, or delete goals.
Goals marked as “completed” will be crossed out and highlighted in green.
Future updates will support automatic sprint goal detection from Jira issues.
2️⃣ Sprint Velocity & Predictability
This enhanced velocity chart shows data from the last 5 completed sprints.
You’ll see:
Committed vs Delivered story points for each sprint
Average Delivered (horizontal line)
Average Predictability % (how closely your team meets their commitments)
Change Since Last Sprint (increase or decrease in predictability)
💡 This visual helps teams understand delivery consistency and predictability trends - ideal for sparking meaningful retrospective conversations.
3️⃣ Sprint Scope Changes
A breakdown of what was added, completed, or left incomplete in the selected sprint, compared to the previous one.
Features:
% change indicators to show if you improved vs. last sprint
Filters by issue type or issue name
A detailed table of all issues with category tags (Added / Completed / Incomplete)
🔍 Carryover Detection:
Issues carried over from previous sprints are clearly marked, including how many sprints they've been carried forward (e.g. “Carried Over +2”). This helps surface long-standing blockers.
4️⃣ Cycle Time Analysis
A powerful tool to uncover bottlenecks and process inefficiencies.
Choose any combination of your Jira status columns (e.g. To Do, In Progress, Done) and SprintRetro will display:
Average Time in each status
Median Time
Min / Max Time
% Change vs Previous Sprint
💡 Helps teams identify delays in handoffs, QA, or reviews that may not be obvious from burndown charts alone.
❗ Important notes:
If multiple statuses are selected, only issues that passed through all selected statuses are counted.
SprintRetro uses a 24/7 timer - weekends and non-working hours are included for full visibility.
5️⃣ Sprint Burndown Chart
Unlike Jira’s basic daily burndown, SprintRetro tracks every individual story point change in real time - second by second.
This chart:
Reflects exact moments work was added, removed, or completed
Provides a true narrative of sprint progress
Great for walking teams through what actually happened, step-by-step
6️⃣ Status Overview
To reduce complexity, SprintRetro aggregates your Jira statuses into the 3 core states:
To Do
In Progress
Done
Even if your workflow has 10 custom statuses, this simplifies the view so teams can easily understand issue distribution across the sprint.
🔁 Always Available - Even Outside Retros
The Sprint Metrics Panel also works beautifully with our Sprint Risk Tracker board template - making it useful for in-sprint reviews as well. You don’t need to be running a formal retrospective to use this metrics suite.
Some teams even keep the panel open full-time with a lightweight template for ongoing inspection.
📘 Learn more about the Sprint Risk Tracker Template →
🔄 Next Up
Ready to turn insights into action?