9 effective team exercises for agile retrospectives

Goal: Create an initial feedback format with safe participation for everyone.

When is the exercise a good fit? If your team is reserved or if some people rarely express how they are feeling and what they think.

Duration: 5-10 minutes

Process:

1. Provide a simple scale, for example colors (🟢 - 🟡 - 🔴), emojis (🤩 - 😊 - 😕 - 😩), or numerically from “1 = 👎” to “5 = 👍”.

2. Then present a statement for reflection to the group and ask for a rating. Depending on the format of the team meeting and the scale, the wording could be something like this:

   • In a weekly on Monday: “How confident are you going into the week?”
   • In a weekly on Friday: “How satisfied are you with this week?”
   • In a daily standup in the morning: “How much energy do you have for your tasks today?”
   • In a (sprint) review: “How do you rate the value delivered to the customer from this iteration?”

3. Each person gives their rating in turn and, if they like, adds one or two sentences.

4. As the moderator, you briefly thank them, but do not open a discussion about the individual comments.

It is also best to announce right away that you will now do this mood check-in regularly in order to create an open space where people can share themselves and everyone is heard.

Of course, team members will not suddenly be able to open up automatically and openly express how they feel. But the format does at least help team members ask themselves: How am I actually doing in relation to my work? And why?

That is a necessary first step.

Facilitation notes:

• Start with your own assessment and lead by example.
• Keep contributions brief.
• Do not assess mood.
• No one should be pressured to give reasons.

How you notice the benefit: The group becomes more human and more familiar. The initial reluctance to speak up decreases.

Goal: Make appreciation visible and create a safe basis for discussion.

When is the exercise a good fit? If the team quickly turns to criticism or if mutual appreciation is rarely expressed.

Duration: 15–20 minutes

Process:

1. Each person notes one or two observations about helpful behavior in the team. Important: This is about specific situations, not general praise.
2. Everyone presents their cards to the group. After each presentation, place the cards on a board and group similar examples together.
3. At the end, discuss: “What should we consciously do more often?”

Facilitation notes:

• Ask for concrete examples.
• Praise behavior, not personality traits.
• If things go quiet, offer a few harmless examples of your own to get things started.

Moderation questions:

• What has recently made work easier for you?
• Who recently helped you in a particularly helpful way, and how?
• When have you felt supported in the team?

How you notice the benefit: The team sees the strengths of individual team members, too, despite all the problems.

Goal: Develop a shared picture of good feedback practice in the team.

When is the exercise a good fit? If feedback is rare, often comes too late, or is quickly understood as an attack.

Duration: 20-30 minutes

Process:

1. Divide a board into three columns: Occasions, giving feedback, receiving feedback
2. On the left, collect occasions for feedback. For example: mistakes, misunderstandings, conflicts, or successful collaboration.
3. In the middle, collect rules for how feedback should be given.
4. On the right, collect ideas about how feedback should be received.
5. Then the team marks the two to three most important points per column.
6. Hang the map somewhere visible or save it in a place everyone can find.

Moderation questions: The following points should later be answered on the board:

• When should we give feedback directly in the moment, and when is it better later (one-on-one)?
• What helps you not to hear feedback immediately as a reproach? How should we give feedback so that it is constructive?
• How can we lower the barrier to giving feedback?
• How should one react to feedback? How do you show the other person that you are also taking the feedback on board?

Use the opportunity as well to give each other feedback in a role-play and practice the points.

How you notice the benefit: Feedback becomes more predictable. The team gains clarity about how to give and receive feedback.

Goal: Reduce inhibitions to ask questions and make uncertainty visible.

When is the exercise a good fit? When the team often silently assumes instead of asking openly.

Duration: 15–20 minutes

Process:

1. As a relaxed warm-up, collect examples of “silly questions” that someone else asked, so you no longer had to ask them yourself.
2. Each person writes anonymously on a moderation card: a question they once didn’t dare to ask in their day-to-day work.
3. The cards are collected and read aloud.
4. The team discusses:
   • Why might someone hesitate to ask this question?
   • What would have been the downside if it had never been asked?
   • What would have been the benefit?
5. To conclude, the team answers the question: “What can we do as a team to make it easier to ask such questions?”

Facilitation notes:

• Make sure to really preserve anonymity.
• Respond appreciatively to every question.
• Allow laughter about situations, but not about people.

Moderation questions:

• Which of these questions would probably have been asked by several people as well?
• What does it cost us as a team when questions go unspoken?
• What could be a simple rule to make follow-up questions normal?

How you notice the benefit: The team realizes that uncertainty is normal. Questions feel less embarrassing and more like a contribution to learning.

Goal: Take the taboo out of openly talking about mistakes and put learning and improvement at the forefront.

When is the exercise a good fit? When the team takes mistakes personally right away or when problems are usually only talked about in passing.

Duration: 20-25 minutes

Process:

1. Each person thinks of a small mistake, a misunderstanding, or an unnecessary detour from day-to-day work.

2. Each person briefly notes:

   • What happened?
   • What did I learn from it?
   • How can my learning help the team in the future?

3. The examples are shared one after another.

4. The moderator collects common patterns.

5. At the end, the team chooses one or two small lessons it wants to test in everyday work.

Facilitation notes:

• Explicitly ask only for small, safe examples.
• Step in if the round turns into justification or blame.
• Make openness visibly appreciated.

Moderation questions:

• What about this mistake was more annoying than dramatic?
• What helped you learn from it?
• What could the team have seen or done earlier?
• What small habit would make similar mistakes less likely?

How you notice the benefit: Mistakes become a little more normal. The team practices learning from situations instead of only judging someone.

Goal: Address contradictions and unspoken issues constructively.

When is the exercise a good fit? When uncomfortable topics are avoided in the team and known problems are too rarely addressed openly.

Duration: 20-25 minutes

Process:

1. Explain the concept of the elephant in the room: “Every team has problems that everyone knows about, but that are still rarely mentioned.”
2. Each person writes anonymously:
   • an elephant in the room
   • or an issue that the team rarely talks about openly
3. All cards are collected, read aloud, and grouped together.
4. Joint reflection on the result:
   • What patterns do we recognize in the topics we are reluctant to address?
   • What makes it so difficult to address these topics?
   • With which elephants would it make the biggest difference if we addressed them more openly in the future?
   • What things do we want to address more openly in the future than before? What can we do as a team to make speaking up easier?
5. In a closing round, everyone shares in turn: “What did it feel like to name the elephants in the room?”

Facilitation notes:

• Anonymity is especially important here.
• Let the group first see patterns before talking about solutions.
• If a topic is too sensitive for the group, park it neatly for a suitable setting.

Moderation questions:

• Which topics have been draining our energy for a while now?
• Which topics are uncomfortable, but important?
• What makes it difficult to speak openly about exactly that?
• What would be a safe next step for one of these topics?

How you notice the benefit: The team is training exactly the skill that retrospectives will later need: making uncomfortable truths visible without attacking people.

Goal: Establish shared ground rules for respectful, open, and learning-oriented collaboration.

When is the exercise a good fit? When expectations and standards in the team are unclear and lead to conflicts or tensions.

Duration: 30-45 minutes

Process:

1. Present the team with three guiding questions or adapt them as you see fit:

   • What is important to us so that we feel comfortable as a team and can work together openly, honestly, and respectfully?
   • In which situations are we lacking common standards or rules?
   • Which conflicts could we avoid by creating more clarity?

2. Individual brainstorming: Each person first gathers their own thoughts in silence.

3. Then discuss the answers together and cluster similar points.

4. Use dot voting to identify the most important points with the greatest need for action, and formulate your team norms from them.

5. Keep the norms clearly visible and agree on how you will address violations in everyday work and when you want to review them again next time.

Facilitation notes:

• Formulate rules so that a rule violation can be clearly recognized and named.
• Less is more. Five clear rules are better than fifteen vague wishes.
• Question every rule critically: “Does this rule really make a difference for us?” and “Why is this rule important for us?” Avoid keeping rules that are currently unproblematic anyway.

Moderation questions:

• What is important to us so that we feel comfortable as a team?
• Which rules would make us a better team if we all followed them together?
• Which points from the previous exercises (e.g. giving and receiving feedback, dealing with mistakes) should we incorporate?
• How do we deal with it when rules are not followed?

How you notice the benefit: The team has a shared language for expectations. Feedback can be based on agreements rather than vague impressions.

Goal: Translate agile values into observable behavior.

When is the exercise a good fit? If agile terms feel rather abstract within the team or if you want to reflect on collaboration more consciously.

Duration: 25-35 minutes

Process:

1. Write the five agile values visibly on the board: courage, respect, openness, focus, and commitment.

2. The team collects concrete behavioral examples from everyday life for each value (a mind map for each value is recommended).

3. Then discuss:

   • What are we already doing well?
   • What is still difficult for us? / What could we do better? (And how?)

4. For each value, define a behavioral anchor that makes visible for you how this value is lived in the team. Here are some examples for inspiration:

   • Courage:
     • We address problems, risks, and conflicts early on.
     • We critically question existing ways of working.
     • We openly admit mistakes and take responsibility for them.
     • Where appropriate, we also make decisions with incomplete information.
   • Respect:
     • We listen to one another attentively and let each other finish speaking.
     • We treat differing opinions with appreciation.
     • We always assume positive intentions on the part of others.
   • Openness:
     • We make progress, obstacles, and mistakes visible.
     • We are willing to change and question our perspectives.
     • We address uncertainty and gaps in knowledge.
   • Focus:
     • We consistently bring started work to completion.
     • We stay on topic during discussions.
     • We protect our attention and working time from distractions and interruptions.
   • Commitment:
     • We keep our commitments and proactively communicate deviations.
     • Each of us acts in line with our agreed priorities and goals.

5. Finally, choose one value / behavioral anchor that you would like to implement more strongly in everyday life.

Facilitation notes:

• Keep the discussion grounded in everyday life and always ask about observable behavior.
• Avoid theoretical lectures and hair-splitting.

How you notice the benefit: The team reflects not only on processes, but also on behavior. That is exactly what makes later retrospectives more valuable.

Goal: Create a shared understanding of iterative work and strengthen the team’s sense of self-efficacy.

When is the exercise a good fit? When the team quickly demands big solutions or often feels they can influence little to nothing.

Duration: 20-30 minutes

Process:

1. Choose a few example topics that should be improved, preferably well-known and recurring problems.
2. Then phrase the desired result in a simple sentence.
3. Now collect many small steps that one could take could, to get closer to a solution.
4. Choose only the smallest meaningful first step that can be carried out within the next few days, at most weeks.
5. Clarify:
   • Who will try it?
   • By when?
   • How will we know whether it was helpful?

Facilitation notes:

• Stop overly large measures and break them down into individual steps
• Gather many alternative suggestions
• Keep the impact manageable and observable

Moderation questions:

• What is the smallest thing we could try for this?
• What change is so small that we can make it this week?
• What information, approval, or whose support are we missing in order to be able to implement a solution?
• Which stakeholders are involved in this problem? Who could we talk to?
• How would we know that this step has helped?
• What can we influence ourselves, without waiting for a major approval?

How you notice the benefit: The team experiences greater room to act. Improvements feel achievable. Small progress becomes noticeable.