Sprint Diagnostics
A diagnostic format that combines a quick rating with focused discussion. The team scores the sprint on dimensions like communication, collaboration, quality and pressure, then names a standout like or dislike and what could be done differently before agreeing on actions. The numbers give an easy way to track how the team's health changes over time.
A number plus one sentence on what drove it
Roman
7 — communication fine, quality slipped under deadline pressure
Maria
5 — collaboration good, but pressure was high all sprint
The single strongest positive or negative moment of the sprint
Anna
Big like: the incident review with no blame, only fixes
Daria
Big dislike: finding out about the scope change on Friday
Improvements phrased as a change, not a complaint
Maria
Freeze scope after planning, exceptions go through the PO
Kirill
Split tickets so nothing takes more than two days
Owner and date for each change the team agreed on
Daria
Ana adds a scope-change rule to the team agreement by Friday
Roman
Split the migration ticket into four before next planning — Tom
Sprint Rating
- Communication:
- Collaboration:
- Quality:
- Pressure:
Big Like/Dislike
- Event:
- Explanation:
Improvements
- What could we do better/differently?
- How can we implement the changes?
Action Items
- Steps to be taken to improve the next sprint.
Similar templates
Other formats teams pair with this one — open any of them as a board in one click.
3 L's
A lightweight three-column retrospective for teams that want quick, honest feedback. Participants capture what they liked, what they learned and what they lacked during the sprint. Stripped down to the essentials, it's an easy starting point for teams new to retrospectives or short on time.
DAKI
DAKI gives the team four clear levers for change in a single view. Participants decide what to drop because it no longer helps, what to add that's missing, what to keep that works well and what to improve. The crisp structure makes it easy to leave the session with a concrete, balanced set of adjustments.
SWOT Analysis
A strategic format borrowed from business analysis and adapted for team reflection. The team maps its strengths and weaknesses against external opportunities and threats to see the bigger picture. It works especially well for longer horizons — a quarter, a release or a project — where strategy matters as much as day-to-day fixes.
The Good - The Bad - The Ugly
A vivid three-part format that makes room for things the team can't simply fix. The good is what worked well, the bad is what went off plan, and the ugly is what lies outside the team's control but still deserves to be named out loud. That third column is what sets it apart, surfacing systemic issues that other formats tend to skip.
Agile Kanban
A retrospective that borrows the familiar Kanban board to review the team's flow of work. Items move across to do, doing and done, making bottlenecks and stalled tasks easy to see. It's a natural fit for teams that already think in terms of flow and want their reflection to mirror how they actually work.
Six Thinking Hats
Based on Edward de Bono's method, this format has the team look at the sprint through six distinct mindsets. Each hat directs attention to one angle — facts, feelings, caution, optimism, creativity and process — so the discussion stays balanced and no perspective is missed. It's a powerful way to break out of habitual thinking and explore an issue from every side.
