An agile retrospective is a regular team format in which different perspectives on how the team works together are gathered, interpreted and turned into concrete next steps. It follows five phases: setting the stage, gathering data, generating insights, deciding what to do and closing. What makes it work is a frame of trust that allows people to share openly in the first place.
Key Takeaways
- Retrospectives that never change their focus keep producing the same results: if you run every retro with the same questions at the same level, you get the same answers and no new insights.
- Action items usually fail not for lack of will but because they are too abstract. A concrete next step, such as writing an email or scheduling a meeting, gets more moving than a big goal.
- The five phases of a retrospective (Set the Stage, Gather Data, Generate Insights, Decide What to Do, Close the Retrospective) aren’t a formality. They prevent the most common mistake: jumping to interpretation before every perspective is in the room.
- It makes sense to start designing a retrospective with the third phase. Once you know what kind of insights you need, you can shape the check-in and the opening to match, instead of the other way around.
What Sets a Retrospective Apart from a Workshop
In an agile retrospective, a team learns from its past experience of working together by reflecting on it as a group. The key word is “together”: reflection doesn’t happen inside one person’s head but in a room where several people share their different perceptions.
Sabina Lammert compares it to the parable of the six blind men and the elephant. One feels a rope, the next takes a leg for a pillar, a third thinks it’s a bed. Each has a different perspective, and only by putting those perspectives together do you get a picture that comes closer to the truth.
Two things distinguish a retrospective from an ordinary workshop: its dramaturgy and its repetition. A retrospective follows a deliberate structure that opens a space where people are willing to share honestly. And it comes back at regular intervals. That steady rhythm builds trust over time.
Why Continuous Reflection Pays Off
If you don’t take the time to hear different perspectives, in the worst case you make the same mistakes over and over. Continuous improvement isn’t an agile ritual for its own sake. It’s what it takes to become and stay economically viable.
The only constant is that circumstances change. Even a team that has worked well together for a long time operates in an environment that keeps shifting: politically, technically, or through unexpected events like a pandemic. Without stopping regularly to reflect, a team can drift off course without noticing and may no longer be able to correct in time.
That makes a retrospective something like a team’s health check. And its result may well be: everything’s fine, we’ll carry on as before. In that case, that’s exactly the right insight.
Trust Is the Precondition, Not an Extra
A retrospective only works in a space of trust. Anyone who shares a perspective needs to be sure they’ll be heard and won’t be put down for what they say.
Two agreements hold that space together. The first is the Prime Directive, formulated by Norman Kerth: the basic assumption that everyone did the best they could under the given circumstances. If something isn’t right, the team works on the circumstances, not on the individual.
The second is the Las Vegas rule. What happens in the retrospective stays in the retrospective. Sensitive information only leaves the room if everyone explicitly agrees.
Neither can be forced. In a first retrospective, nobody shares anything confidential, and that’s fine. Only as the format is cultivated do moments arise over time where participants show vulnerability and say: I made a mistake. If the team responds constructively, mistakes become visible earlier and the team can deal with them better.
The Five Phases of an Agile Retrospective
A retrospective follows five phases, described by Esther Derby and Diana Larsen. This structure is the difference between a talk session with little to show for it and real improvement.
| Phase | Name | Purpose |
|---|---|---|
| 1 | Set the Stage | Open the space, let people arrive, shape the setting |
| 2 | Gather Data | Collect perceptions, give every perspective a voice |
| 3 | Generate Insights | Interpret the data collected |
| 4 | Decide What to Do | Agree on concrete next steps |
| 5 | Close the Retrospective | Wrap up, cool down, clarify confidentiality |
Phase one is about literally shaping the space: chairs in a circle or not, online or on site, flip chart or sticky notes. Participants should be able to arrive and let go of other worries.
Phase two is the step that often gets skipped. Before anything is interpreted, the team collects the individual perceptions: the rope, the pillar, the bed. Only this collecting reveals that there’s something bigger behind them, the whole elephant.
One of the most common mistakes is jumping into interpretation too quickly. That’s exactly why phase two needs time and space, so that everyone really gets a say.
Why Action Items Fail When They’re Too Big
Action items from retrospectives often go nowhere because they’re too big. If you try to jump straight from the status quo to the target picture, you end up with something so abstract that nobody acts on it. Then everyone wonders why nothing happens.
The more effective route is the concrete next step. Instead of one giant action item, this is enough: write an email, schedule a meeting. Really small. This mindset comes from solution-focused coaching, and it noticeably raises the hit rate.
A second reason action items stay undone lies outside the team’s own sphere of influence. The Circle of Influence helps here: what can the team influence itself, and what not? If the original action item falls outside it, the next step might be to talk to someone within whose sphere it does fall. This kind of working through intermediaries is often unavoidable in organizations.
What to Do When the Same Sticky Notes Come Up Every Time
When retrospectives always deliver the same results, it’s usually because of the same questions asked at the same level every time. If you ask “What went well, where can we improve?” about the whole sprint every single time, you get the same surface back every single time.
The fix is to change the focus. Instead of working through twenty topics per session, the team picks one topic, such as meetings or the interface with sales, and goes deep. Real conversations only start when the level of detail goes up.
If a team hasn’t implemented anything from one retrospective to the next, that itself can become the topic. A retrospective on the action items of the last retrospective gets to the cause: was the action item too big? Was it outside the team’s sphere of influence? Was someone missing, knowledge, skills?
It’s also important to check in every follow-up retrospective whether the agreed steps were actually taken. If you only come up with new action items without checking whether the old ones worked, you’re going in circles.
From Format to Design: Start with the Goal
Choosing the right method doesn’t start with the format but with the goal of the retrospective. Only then comes the question of which exercise supports that goal. Method collections like Corinna Baldauf’s Retromat offer plenty of formats for every phase, but not every format fits every goal.
For this, Sabina Lammert developed a design canvas, meant as a starting aid rather than a tool for pros with hundreds of facilitated retrospectives behind them. The approach flips the usual order: the design starts with phase three, the insights you want to reach. From that target picture, the rest is built backwards.
The model comes from yoga. There, a peak pose demands particular strength or flexibility. If you know what you’re working toward, you build the warm-up accordingly, so nobody gets hurt. For retrospectives, that means the opening depends on the result you’re aiming for.
The canvas distinguishes four kinds of retrospectives, each calling for a different opening:
- Analytical: It’s about understanding data. The check-in speaks to the analytical part of the brain.
- Emotional: There’s a conflict or different perceptions of a situation. The opening is low-threshold and helps people connect with their own feelings.
- Creative: Solutions should come from outside the usual tracks. Then the first phase starts creatively, too.
- Hands-on: The team needs to get to action quickly and work associatively rather than overthinking.
“If I know what I’m working toward, I have to adjust my warm-up accordingly. At some point, that became woven into the way I design my retrospectives.”
(Sabina Lammert)
Always Adapt the Method to the Team
Who you’re working with counts as much as the goal. Some teams don’t want to jump around in a circle or build with Lego, and that reluctance belongs in the design.
Lego is a good example of a method that’s burned in many organizations because badly run Lego workshops have already taken place there. Even a committed Lego fan should then reach for a less playful, more analytical method, so participants don’t walk in with reservations.
As an external facilitator, Sabina gets a feel for this through preliminary conversations. Helpful questions: what workshops have you had before? What went down well, and what didn’t work at all? If you know the team yourself, you have an advantage here and know what has worked in the past.
The way forward is feeling your way in. From one retrospective to the next, you can dare a little more: a small game, a visual exercise, a theme. Starting with a completely over-the-top themed retrospective, with an unfamiliar team that has bad experiences behind it, can easily go wrong.
How to Get Started with Retrospectives as a Beginner
If you’re just starting with retrospectives, deliberately reduce the complexity. The number of options, five phases, countless formats and free combinations, is overwhelming at first.
Three things help you get going:
- Co-facilitate with someone experienced. Watching how they do it lowers the barrier considerably.
- Find a sparring partner. There’s often someone in your own organization with experience who’s worth talking to.
- Take part yourself. Having experienced one really good retrospective makes a huge difference.
Frequently Asked Questions
Does a team that works well together even need retrospectives?
Yes. Even when collaboration is consistently strong, the circumstances change, whether due to political or technical factors, or unexpected events. Without taking regular time to reflect, a team can drift unnoticed in the wrong direction and may no longer be able to correct course in time. A retrospective acts as a health check for the team. Its conclusion may explicitly be: Everything is fine; we’ll continue as before.
What encourages participants to speak openly in a retrospective?
Two agreements set the tone. Norman Kerth’s Prime Directive assumes that everyone has done their best given the circumstances: If something isn’t right, the team works on the conditions, not on the individual. The Las Vegas Rule keeps what’s said within the room. This can’t be enforced; in a first retrospective, no one shares anything confidential.
What’s the most common mistake made in retrospectives?
Jumping to conclusions too soon. Before any interpretation takes place, individual perceptions must first be gathered. In the parable of the six blind men and the elephant, one feels a rope, another mistakes a leg for a pillar, and a third believes it to be a bed. Only by piecing them together does it become clear that there is something larger behind it all.
What should you do if an action falls outside the team’s sphere of influence?
Then the next step shifts: it’s not the action itself, but rather the conversation with someone within whose sphere of influence it falls. The Circle of Influence distinguishes between what the team can influence and what it cannot. This passing the buck is often unavoidable in organizations and is one of the two main reasons why agreed-upon actions remain unaddressed.
How do you go from the surface to the deeper level in a retrospective?
By focusing on a single topic (such as meetings or the interface with Sales) instead of working through twenty topics per session. In-depth discussions only emerge when the level of detail increases. If you ask every time what went well and where there’s room for improvement, and do this for the entire sprint, you’ll get the same superficial answers every time.
What’s the best order to plan a retrospective?
Backward, starting with phase three. If you first clarify what kind of insights are needed, you can tailor the check-in and opening accordingly. The analogy comes from yoga: If you know your peak pose, you can structure your warm-up accordingly. Analytical, emotional, creative, and hands-on retrospectives each require a different approach to the opening.
How do you choose a method if a team has had bad experiences with workshop formats?
Opt for a less playful, more analytical method, even if you’re a big fan of the other format. Lego has been discredited in many organizations because poorly executed Lego workshops were held there in the past. Preliminary discussions provide the necessary insight: What workshops have been held in the past, what went well, and what didn’t work at all? From there, you can take more risks from one retrospective to the next.
