Retrospective meetingagenda, roles, and ground rules
Run a retrospective meeting with a timed agenda, clear roles, practical ground rules, room for quieter evidence, and an owned next step that survives the call.
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 under review.
- Pick a fitting format.
- Invite the people who shared the work and can improve its system.
- Bring the previous action and useful delivery evidence.
- Decide if cards are named or anonymous before the call, then explain the choice clearly when the session opens.
A 40-minute retrospective meeting agenda
- Open and review (5 minutes): restate the purpose, then check what happened with the previous action since the last meeting.
- Write silently (7 minutes): one observation per card.
- Read and group (8 minutes): clarify what each card means and gather shared patterns.
- Vote (4 minutes): rank the themes.
- Discuss (11 minutes): examine the causes, impact, and options behind the leading theme.
- Commit and close (5 minutes): name the action, owner, timing, and review signal that the team will check next time.
Choose a 30-, 45-, or 60-minute retro agenda
| Length | Best for | Suggested timing |
|---|---|---|
| 0130 minutes | A small team reviewing a routine sprint | Open for 3 minutes, write for 5, group and vote for 7, discuss for 10, then commit for 5 |
| 0245 minutes | A normal sprint with several themes | Open for 5 minutes, write for 7, group and vote for 10, discuss for 17, then commit for 6 |
| 0360 minutes | A larger group, release, incident, or sensitive topic | Open for 8 minutes, write for 10 minutes, group and vote for 12 minutes, discuss for 22 minutes, then commit for 8 minutes |
If time runs short, trim collection and grouping first. Keep the final commitment. A focused 30-minute session can still produce a useful experiment when the team gives it an owner and a review point.
Open with one purposeful check-in
Choose one question that fits the meeting. "What would make this retrospective useful?" brings expectations into the open. "What feeling best describes the last sprint?" helps the facilitator read the room. Keep the round under five minutes, let anyone pass, and use 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. Feedback belongs to the team. Participants bring evidence, ask clarifying questions, and help choose a workable experiment. The action owner coordinates the next step, with other people doing parts of the work as needed.
Adjust those roles 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. Leave labels off people.
- Let anyone pass on a prompt, with no explanation required.
- Give speakers room to finish and protect the authors of anonymous cards.
- Clarify first, then disagree.
- Keep actions within the team's influence.
- State the confidentiality boundary plainly, including what may leave the room.
Remote retrospective meetings
Send the board link before the call, use a visible timer, collect cards silently, and reveal contributions together. Camera use says little about 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 cuts setup time. Try Classic Sprint for a first meeting, Start Stop Continue for direct decisions, or Safety Check when hesitation needs careful handling.