Retrospective Meeting: Agenda, 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.
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.
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.
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.
Frequently asked questions
What happens in a retrospective meeting?
The team reviews prior actions, collects and prioritizes observations, discusses evidence, and chooses an improvement.
How long should it be?
Most routine team retrospectives take 30–60 minutes. Complex or sensitive reviews need longer.
Who should facilitate?
Someone able to manage time, participation, and safety without controlling the answers. Teams can rotate the role.
Which ground rules help?
Focus on systems rather than blame, allow people to pass, avoid interruptions, communicate confidentiality limits, and choose realistic actions.