Team Retrospective
Help your team reflect on what worked, what didn't, identify root causes, and commit to concrete improvement experiments.
Session
Team Retrospective
Help the team reflect on what worked, what did not work, identify root causes, and agree on concrete improvement experiments.
Facilitator guide
Set the context, then invite each participant to share their top priority before opening discussion.
Step 2 of 4 · 18 min left
Decisions & next steps
Overview
Help the team reflect on what worked, what did not work, identify root causes, and agree on concrete improvement experiments.
Expected outcome: A clear list of improvement actions, team experiments, owners, and a follow-up date..
When to use it
- End of a sprint or cycle
- After a major release or milestone
- Resetting team working habits
Who should attend
Team lead, product team, delivery team and a scrum master — the people who did the work.
Preparation checklist
- Frame it as improvement, not blame
- Collect metrics or data in advance
- Prepare a shared board for notes
Example agenda outline
- 0:00–0:10
Welcome and safety
Frame the goal and ground rules.
- 0:10–0:25
Silent reflection
Individual start/stop/continue notes.
- 0:25–0:45
Sharing and clustering
Group themes on a shared board.
- 0:45–1:10
Root-cause discussion
Dig into the top two or three themes.
- 1:10–1:25
Experiment selection
Pick 1–3 small experiments to try.
- 1:25–1:30
Owners and follow-up
Assign owners and set the next check-in.
Facilitation tips
- Start with silent reflection so every voice is included
- Keep experiments small and testable
- Always assign owners and a follow-up date
Common risks
- Blame replacing learning
- The same issues repeating with no action
- Experiments with no owners
Expected outcome
A clear list of improvement actions, team experiments, owners and a follow-up date.
Use the Team Retrospective structure for your next session
Sign up and generate a complete facilitation plan from this template.
Templates for this type of meeting
Retrospectives that lead to real improvement
A retrospective should turn honest reflection into a few concrete experiments. Without psychological safety and structure, it becomes a complaint session that changes nothing.
Read moreTeam workshops that create alignment you can see
Team workshops build shared understanding around roles, expectations and ways of working. Without structure, they surface friction without resolving it.
Read moreA retrospective meeting agenda that creates change
A retrospective should turn reflection into a few real experiments. This agenda protects psychological safety and ends with owners and a follow-up date.
Read moreHow to facilitate a meeting well
Facilitation is the difference between a meeting that decides and a meeting that drifts. This guide covers preparation, running the room, handling difficult moments and closing with action.
Read more