Sprint retro one-pager
Resource · Generic template · No client data
Use this in your own team or workshop. It stays deliberately generic: replace Team name, Sprint dates, and timeboxes with your reality. The goal is a single, shared improvement to try in the next iteration—not a list of every complaint.
Before the room (5–10 min)
- Confirm the sprint goal and what shipped (or what did not) without blame.
- Decide: async input first, or all live? Pick one so quiet voices are not steamrolled.
- Prime the team: we are here to improve the system, not to score points on people.
Suggested timeboxes (60 min total)
- Set the stage (5 min) — Restate the sprint goal; agree on one working agreement for this hour (e.g. “assume good intent”).
- Gather data (10 min) — What happened? Use facts, demos, or board snapshots instead of adjectives only.
- Decide what it means (15 min) — “What got in the way of the goal?” Cluster themes; do not try to fix everything.
- Choose actions (20 min) — For the top 1–2 themes: owner, first step, and how we will know it helped.
- Close (10 min) — One appreciation; confirm where notes live; schedule any follow-up.
Prompts that usually work
Data: “What evidence would a visitor see on our board or in our demo?”
Handoffs: “Where did work wait, or get reworked?”
Clarity: “When did the sprint goal get fuzzy for you?”
Single improvement: “If we can only change one thing before next sprint, what is it—who will try it, and on what day?”
Anti-patterns to name out loud
- Solutions before shared understanding.
- Anonymous blame (“someone should have…”).
- Action items with no owner, no week, and no way to see if they landed.