Templates · Essentials
Sprint Diagnostics
Everyone rates the sprint, names its strongest moment and proposes changes; the board ends on agreed actions.
- How was this sprint? Rate it 1–10 (communication, collaboration, quality, pressure) A number plus one sentence on what drove it
- Big like or big dislike The single strongest positive or negative moment of the sprint
- What could we do even better or differently? How? Improvements phrased as a change, not a complaint
- Actions Owner and date for each change the team agreed on
What it is
A guided sequence more than a sort. The four columns follow the order of a diagnosis: a rating of the sprint from 1 to 10, looked at through communication, collaboration, quality and pressure; then the strongest moment; then what could be done better; then the actions.
Goal
A reading of the sprint in numbers that can be compared from one person to the next, each backed by a reason, and a list of changes with owners.
When to use it
- When the team wants to check its health with the same questions sprint after sprint.
- When opinions about a sprint diverge and you want to see how far apart they are.
- With quiet members: a number and one sentence are easy to give.
When to pick another format
A rating exposes its author. If people are not comfortable giving a low number, run a Safety Check first, or use Went well, To improve, Action ideas, which asks for no score. If the sprint had one big problem that needs depth, take Fishbone Analysis.
How to run it
- How was this sprint? Rate it 1–10 (communication, collaboration, quality, pressure) Ask each person for a number plus one sentence on what drove it. Agree beforehand whether people give one overall number or one per angle.
- Big like or big dislike: one card per person, the single strongest positive or negative moment of the sprint.
- What could we do even better or differently? How? The “How?” matters: an improvement is phrased as a change, not as a complaint.
- Actions: an owner and a date for each change. What people write here are proposals until the discussion confirms them.
Start with the ratings, and look at the spread before the average: a lone low number deserves a question, not a defence. Go through the strong moments next, then group and vote on the improvements, and close on the actions the team agreed on.
Columns
| Column | Description |
|---|---|
| How was this sprint? Rate it 1–10 (communication, collaboration, quality, pressure) | A number plus one sentence on what drove it |
| Big like or big dislike | The single strongest positive or negative moment of the sprint |
| What could we do even better or differently? How? | Improvements phrased as a change, not a complaint |
| Actions | Owner and date for each change the team agreed on |
To start a retrospective from this template, see Create a retro.