RETROSPECTIVE MEETING TEMPLATE
Retrospective Meeting Template — Free Sprint Retro Agenda
A timed 60-minute retrospective meeting template with eight proven retro formats, a copy-paste question bank, and an action rule that ends with owners instead of complaints — download the free .docx or copy the agenda below. Want the notes written for you? VocalFuse drafts them from a local transcript: no meeting bot in the room, no audio upload, flat pricing from $5/mo.
New to retros? The sprint retrospective is the meeting where the team inspects how it worked — this template runs the classic five-phase arc (set the stage, gather data, generate insights, decide, close) in 60 minutes flat.
The 60-minute sprint retrospective agenda
Five phases, fixed times — the standard agile arc. The discipline is the point: silent writing equalizes participation, dot-voting picks what the room actually cares about, and the meeting ends by spending its limited influence budget on one or two owned actions — not a list of ten with no names on them.
| Phase | Time | What it covers |
|---|---|---|
| 1. Set the stage | 5 min | One-word check-in around the room, then restate the prime directive: everyone did the best job they could with what they knew at the time. Safety first — candor does not survive a hostile opening. |
| 2. Gather data | 15 min | Silent writing against the format's prompts (start-stop-continue, 4Ls, mad-sad-glad...), then each person shares their top item. No discussion yet — collection only, two minutes per person max. |
| 3. Generate insights | 15 min | Group duplicates into themes, dot-vote, then discuss only the top two. The facilitator asks "why" until the theme reaches something the team can act on — not just re-describe the symptom. |
| 4. Decide actions | 15 min | Cap it at one or two improvements. Each gets a specific behavior change, a named owner, and a due date inside the next sprint — "communicate better" is a wish; "post the API contract in the channel before the standup" is an action. |
| 5. Close | 10 min | Rate the sprint 1-10 with a show of hands, confirm the actions and their owners, and say how next retro opens: by reviewing these two actions first. A retro whose actions quietly vanish teaches the team the meeting does not matter. |
Running a one-week sprint? A 45-minute variant keeps the same five phases at 5/10/15/10/5; a month-long sprint earns 90 minutes. The rule of thumb is roughly 45 minutes per week of work reviewed.
Free retrospective meeting template (copy & paste)
Plain text on purpose — it pastes cleanly into Word, Google Docs, Notion, Confluence, or your retro board without redesign. Keep the labels, replace the brackets.
RETROSPECTIVE MEETING — Sprint [number] Team: [team]
Date: [date] Time: [start]-[end] Facilitator: [name] Notes: [name]
Period under review: [sprint dates / project phase]
BEFORE THE MEETING
[ ] Last retro's action items pulled up — the review happens first
[ ] Format chosen and posted (start-stop-continue / 4Ls / sailboat /
mad-sad-glad / DAKI / KPT / rose-bud-thorn / lean coffee)
[ ] Prime Directive on the wall: everyone did the best job they could
with what they knew at the time
1. SET THE STAGE (5 min)
Check-in: one word for the sprint
Ground rules: blameless / team-only / timeboxed
2. REVIEW LAST RETRO'S ACTIONS (5 min)
[ ] Action — Owner — Done / In progress / Dropped (if dropped: why?)
3. GATHER DATA (10 min) — silent writing first, cards hidden
[Format prompts per the section below]
4. GENERATE INSIGHTS (15 min)
Group duplicates into themes - blind dot-vote - discuss the top two
Ask "why" until the theme reaches something the team can act on
5. DECIDE ACTIONS (15 min)
[ ] Action: [specific change] — Owner: [name] — Due: [date in next sprint]
Cap: one or two actions. More than three is a wish list.
6. CLOSE (10 min)
Sprint rating 1-10 (show of hands) - actions read back, owners confirm
Next retro opens with: did these two actions happen?
AFTER THE MEETING
[ ] Actions posted to the board/backlog within 24 hours
[ ] Owners confirmed in writing
Eight retrospective formats and when to use each
No format is universally best — each surfaces different signal. Match the format to the sprint you just had rather than rotating on a calendar: a rough sprint calls for Mad/Sad/Glad, a milestone for 4Ls, a routine sprint for Start/Stop/Continue. The anti-pattern is running the same board every sprint until people stop thinking and start pattern-matching.
| Format | Columns | Best for |
|---|---|---|
| Start / Stop / Continue | Start, Stop, Continue | New teams (first 3 sprints) and fast, low-friction retros. Runs 30-45 minutes. The default when nothing is on fire. |
| 4Ls | Liked, Learned, Lacked, Longed for | Milestone retros — end of a release or phase. The Learned column captures reflection most formats skip entirely. |
| Sailboat | Wind, Anchor, Rocks, Island | Teams that need to look forward as much as back: what propels us, what drags, what risks ahead, where we're headed. Visual thinkers. |
| Mad / Sad / Glad | Mad, Sad, Glad | After a rough sprint or incident. Names frustration directly before turning to analysis — use when the metrics look fine but the energy doesn't. |
| DAKI | Drop, Add, Keep, Improve | Mature, process-focused teams auditing how they work. The Improve column captures things worth keeping but not quite right — where most real improvement lives. |
| KPT | Keep, Problem, Try | Experiment-driven teams. Popularized by Japan's agile community; the Try column turns every discussion into a concrete experiment with an owner and a check-in point. |
| Rose / Bud / Thorn | Rose, Bud, Thorn | Balancing good and bad, including with non-engineering teams. Bud (an idea with potential) surfaces forward-looking input the complaint columns miss. |
| Lean Coffee | To Discuss, Discussing, Discussed | A team tired of fixed columns. The agenda is team-voted and timeboxed per topic — the format itself resets engagement. |
Switch when the board repeats
If the same feedback appears every sprint and actions aren't moving, the format isn't the problem — follow-through is. But a format switch resets energy: KPT to force experiments, Sailboat to look forward, back to Start/Stop/Continue when you need speed.
Keep the blameless frame under every format
Whatever the columns, the Prime Directive governs: examine how the system of work failed, not who failed. The moment a retro names a person, silent writing goes defensive and the data dries up.
Retrospective question bank (copy & paste)
Open questions that invite evidence instead of yes/no answers. Silent writing against two or three of these beats a free-for-all discussion — quiet teammates contribute equally.
Process questions
- What went well that we should keep doing?
- Where did we get lucky — and how do we make it repeatable?
- What slowed us down more than it should have?
- What decision do we still owe the team?
- What would we change if we could redo one day of this sprint?
- Which meeting, ticket, or ritual earned its time — and which didn't?
Team & delivery questions
- When did someone help you unblock something this sprint?
- What did we learn that we haven't written down anywhere?
- Where did work sit waiting on a person or a decision?
- What almost went wrong that we caught in time?
- What is the one thing that would make next sprint smoother?
- What are we pretending is fine?
What's in the Word template
The retrospective meeting .docx is a working document, not a screenshot of this page:
- A details table — team, sprint number, date, facilitator, note-taker, period under review
- The 60-minute agenda table with time, coverage, and the outcome each phase must produce
- A before-the-meeting checklist (actions pulled up, format chosen, Prime Directive posted)
- A previous-actions review table with done / in-progress / dropped status
- A themed action-items table — action, owner, due date, which theme it addresses
- The format quick-reference (all eight formats, one line each) and an after-the-meeting checklist
Free download, no email gate — it opens in Word 2016+, Word on the web, and Google Docs.
Have the notes drafted for you — locally
1. Record the retro
VocalFuse transcribes your microphone on your Windows PC with Whisper — no meeting bot joins the call, nothing is uploaded, and it works in Zoom, Teams, Meet, or a physical team room. Candor depends on privacy; the transcript never leaves the machine.
2. Draft the notes
Pro Note Turning turns the local transcript into structured retro notes — themes, action items with owners and dates, dropped-item root causes — in this template's format, ready before the meeting ends.
3. Verify & post the summary
You read, correct names, approve, and post the summary: top themes, the one or two actions, and what was dropped. The team sees themes, not raw quotes — that's what keeps next sprint's retro honest.
Flat pricing, private by design
No per-minute metering and no per-seat math: $5/mo Basic or $10/mo Pro. Audio never leaves your machine. See the AI meeting minutes generator.
More free templates — 1:1s, weeklies & retros
The retrospective covers how the team works; these cover the meetings around it. All free .docx downloads — no signup, no email gate.
Sprint retro template
The Scrum-specific sibling: a 60-minute agenda with the review-actions block, five formats, and a copy-paste template.
Sprint retrospective templateOne-on-one template
The private channel the retro can't be: a 30-minute 1:1 agenda with employee-first sections and a 30-question bank.
1:1 meeting templateWeekly team meeting agenda
The heartbeat meeting: a timed 45-minute agenda with a parking-lot rule and a close that produces owners.
Weekly team meeting agendaSkip-level template
The unfiltered-signal meeting: a timed 45-minute agenda, a grouped question bank, and confidentiality ground rules.
Skip-level meeting templateExplore related AI note taking guides
Retrospective meeting template — FAQ
What is a retrospective meeting?
A short, recurring meeting where a team inspects how it worked — not what it shipped — and picks one or two concrete improvements for the next cycle. Most agile teams run it at the end of every sprint; the classic 60-minute shape is 5 minutes to set the stage, 15 to gather data, 15 to generate insights, 15 to decide actions, and 10 to close.
What should a sprint retrospective include?
Five phases: set the stage with a one-word check-in, gather data on the sprint (what went well, what did not), generate insights by grouping votes into themes and discussing the top two, decide one or two actions with a named owner and a due date, and close by rating the sprint and confirming the actions. Keep the data phase silent-writing based so quiet teammates contribute equally.
How long should a retrospective be?
Plan 45 minutes for a one-week sprint and 60 minutes for a two-week sprint; for a month-long sprint, 90 minutes. A reliable rule is about 45 minutes per week of work reviewed. If discussions repeatedly run over, split the formats rather than extend the meeting — a 30-minute start-stop-continue plus a separate deep-dive beats one two-hour session.
What are good retrospective questions?
Open ones that invite evidence: What went well that we should keep? Where did we get lucky? What slowed us down more than it should have? What decision do we still owe the team? What would we change if we could redo one day of this sprint? Avoid yes/no questions — they collapse the discussion before it starts.
What is the difference between start-stop-continue and mad-sad-glad?
Start-stop-continue collects concrete behavior changes: what to begin, what to quit, what worked and should stay. Mad-sad-glad captures emotional reactions first, then works backward to their causes, which surfaces friction start-stop-continue misses. Teams that have run several start-stop-continues in a row often rotate to mad-sad-glad to refresh the discussion.
Should retrospectives be anonymous?
Partially. Silent writing and anonymous voting equalize participation and are standard practice; fully anonymous input between meetings can surface sensitive issues, but there is real risk of unfalsifiable complaints that derail the discussion. The workable middle ground: anonymous contribution during the meeting, attributed discussion and owners afterward.
How do you make sure retrospectives produce real change?
Cap the actions. Pick one or two improvements per sprint with a named owner and a due date inside the next sprint — never a list of ten with no owners. Open the next retro by reviewing the previous actions; a retro whose actions quietly vanish teaches the team that the meeting does not matter. Teams that own their actions report noticeably higher satisfaction than teams where managers assign them.
Can AI write my retrospective notes?
Yes — and locally, which matters for a meeting full of candid feedback. VocalFuse transcribes your microphone on your Windows PC with Whisper: no meeting bot joins the call, no audio is uploaded, and it works in Zoom, Teams, Meet, or a physical room. Pro Note Turning then drafts the notes into this template's structure — themes, actions with owners, follow-ups — and you verify and approve before anything is shared.
Is there a free retrospective meeting template for Word?
Yes — the .docx on this page is free with no email gate. It includes the 60-minute agenda table with outcomes per phase, a facilitator checklist, a start-stop-continue worksheet, a 4Ls board, a question bank, and an action-items table with owner, due date, and status columns. It opens in Word 2016+, Word on the web, and Google Docs.
What is a sprint retrospective vs a sprint review?
The review inspects the product: the team demos working increments to stakeholders and adjusts the backlog. The retrospective inspects the process: how the team worked, communicated, and decided, and what to improve. Reviews look outward at what was built; retrospectives look inward at how the building went. Teams run them back to back at sprint end.