Retrospective meetingagenda, roles, and ground rules
Plan a retrospective meeting with a timed agenda, clear roles, safer ground rules, and concrete follow-through.
A retrospective meeting is a facilitated team session that turns recent experience into a practical improvement. The board supplies prompts, but the meeting design determines whether quieter evidence appears, themes are prioritized, and actions survive after the call.
Before the meeting
- Define the sprint, release, incident, or period being reviewed.
- Choose a format that matches the conversation.
- Invite the people who shared the work and can improve the system.
- Bring the previous action and any useful delivery evidence.
- Decide whether cards are named or anonymous and communicate that clearly.
A 40-minute retrospective meeting agenda
- Open and review (5 minutes): restate the purpose and inspect the previous action.
- Write silently (7 minutes): one observable idea per card.
- Read and group (8 minutes): clarify meaning and merge shared patterns.
- Vote (4 minutes): prioritize across the whole board.
- Discuss (11 minutes): explore causes, impact, and options behind the leading theme.
- Commit and close (5 minutes): assign an action, owner, timing, and review signal.
Choose a 30-, 45-, or 60-minute retro agenda
| Length | Best for | Suggested timing |
|---|---|---|
| 0130 minutes | A small team reviewing a routine sprint | Open 3, write 5, group and vote 7, discuss 10, commit 5 |
| 0245 minutes | A normal sprint with several themes | Open 5, write 7, group and vote 10, discuss 17, commit 6 |
| 0360 minutes | A larger group, release, incident, or sensitive topic | Open 8, write 10, group and vote 12, discuss 22, commit 8 |
Shorten collection and grouping before cutting the final commitment. A fast retrospective that produces no owned next step is only a conversation, while a focused 30-minute session can still create a useful experiment.
Open with one purposeful check-in
Ask one question that matches the meeting: “What would make this retrospective useful?” clarifies expectations, while “What feeling best describes the last sprint?” helps the facilitator read the room. Keep the round under five minutes, let anyone pass, and choose from the meeting check-in question library when the team needs a different opener.
Roles in a retro meeting
The facilitator manages structure, time, airtime, and ground rules. They should not decide which feedback is valid. Participants contribute evidence, ask clarifying questions, and help choose a feasible experiment. The action owner coordinates the next step but does not necessarily perform all the work.
Adjust that structure to the team’s current need. The stages of team development guide shows when to emphasize clarity, productive conflict, shared norms, protected autonomy, or closure.
Ground rules that improve signal
- Describe events, effects, and systems rather than labeling people.
- Let anyone pass on a prompt without explanation.
- Do not interrupt or identify authors of anonymous cards.
- Clarify before disagreeing.
- Keep actions within the team's influence.
- State honestly what will and will not remain confidential.
Remote retrospective meetings
Send the board link before the call, use a visible timer, collect cards silently, and reveal contributions together. Avoid making camera use a proxy for participation. Chat, cards, voice, and reactions can all carry useful input. The remote retrospective guide covers time zones, asynchronous preparation, and participation in more detail.
Closing a finite release, milestone, or cross-functional initiative needs a wider evidence set and durable knowledge transfer. Use the project retrospective guide for that scope.
A ready-made format reduces setup: try Classic Sprint for a first meeting, Start Stop Continue for direct decisions, or Safety Check when hesitation needs careful handling.