6 Retrospective Games Ideas for ambitious Agile Teams

1. As a moderator, you explain the rules to each team member: In front of you on the Echometer whiteboard are some pictures of a frog. Off the top of your head, which one best fits the last sprint? The reasons for choosing a picture don't really matter.
2. Everyone chooses a picture by creating a sticky on the whiteboard by double-clicking.
3. Now everyone briefly explains in one or two sentences why they chose the respective picture. The decision does not have to be "logical" - it is about capturing the emotional state and creating a good atmosphere for discussion.
4. The respective check-in of the team members is neither evaluated nor commented on - but of course laughing is allowed. At most, something interesting is written down in order to use it again in the later part of the retrospective.
5. Now we continue with the next phase of the retrospective, the "Data Collection" (To the article: 5 Phases of a Retro Are Not Enough). Alternatively, you can also look at the measures of the last retrospective together (for example in the Echometer tool).

You can see the basic idea of this retrospective game well on the online whiteboard above, including some examples:

1. First, everyone writes their own name on the Echometer whiteboard. You can create stickies by double-clicking.
2. Now add an adjective to your name that starts with the same letter as your name. If my name is Christian, I could write "The Chameleon Christian," for example. Now add another adjective, which of course also starts with this letter, to form a nice alliteration. In my case, for example: The Charismatic Chameleon Christian.
3. Optionally, you can add something to this addition to your own name, but you don't have to. As I said, the point here is more to create a smile in the room and perhaps to find a new nickname that will survive the next Scrum sprint.

1. As a moderator, you explain the rules to each team member: Based on the emojis and the associated questions, each team member reflects on the last Scrum sprint.
   1. Wow: What caused a "wow" effect for you in the last sprint? It can be both negative and positive.
   2. Wondering: What did you have to think about, were you surprised, were you amazed?
   3. Worried: What worried you or is currently worrying you?
2. Optimally, the feedback is first collected individually and anonymously on the whiteboard (for example in Echometer). You can use the timer and set it to 3 minutes, for example, so that this part doesn't take too long. By the way: With Echometer, this part, the "data collection," can also take place asynchronously before the retro in the form of a digital survey.
3. In the next step, each team member individually presents the results and the further phases of the retrospective are continued: Topics are discussed, prioritized with the help of a voting and measures are derived (To the article: 5 Phases of a Retrospective). The Echometer Retro Tool can help you with all of this.

1. You select a range of statements about behaviors that you think the team could improve (see below, second toggle). These are e.g. the things that are asked in the Spotify Health Check.
2. Of course, you can modify these questions and make some of them funnier or more creative.
3. Everyone indicates how much they agree with these statements on the Echometer scale from 1 to 7.
4. The results are displayed in the graphic. Now everyone is asked to explain the results:
   "From your personal point of view, how do you explain the highest approval? And the lowest voting?"
5. When you have gone through all the points of the Health Check and discussed them, you continue with the typical 5 phases of an agile retrospective.
6. Explain thoughts: After everyone is done with this part, everyone shares their thoughts (and notes) in turn. There is no discussion yet at this point.
7. Prioritization: Each team member has 3 digital points to vote on. Now put the points where you see a need for improvement.
8. Discussion: Discuss the areas that receive the most votes. Would you like to write down a measure?
9. Measures: Name a specific person who is responsible for this measure. I recommend not recording more than 3 measures - focus on quality rather than quantity (more on this in our post 7 tips for good measures).

1. We deliver great results! We are proud of it and our stakeholders are very satisfied.
2. Our way of working suits us perfectly.
3. We get things done really fast. No waiting, no delays.
4. The planning of our sprints is always based on achieving the greatest possible customer benefit in the given time.

5. We also share unfinished work with stakeholders early in order to get feedback as quickly as possible.

6. Every member of the development team is adequately involved in the sprint plannings.
7. We are open to constructive feedback and can grow from it.
8. Courage: We value it when someone shows courage.
9. Respect: We value each other's ideas, even if we disagree.
10. Commitment: Each team member strives to keep promises.
11. Focus: We don't get distracted from pursuing the sprint goal.
12. Openness: We are open to constructive feedback and can grow from it.
13. We have a constructive exchange of knowledge between newer and more experienced colleagues.

1. Each team member marks the place where they were born and another place (if necessary on a digital whiteboard, see above).
2. Timebox 5 minutes: Then the team member comes up with an explanation for both places why they were born there.
   
   For example, Julia Rodriguez could say the following:
   A) As you all know, I was born just around the corner in New York. That's why I work here and visit my family every weekend.
   B) As you all know, my family name is Rodriguez. I actually come from Mexico, where I was born 39 years ago. My family moved to the USA shortly after my birthday because my father started working here.
   Both sound logical - which fact is true?
   
   
3. 1 minute timebox per person: The explanation for the two places is given one after the other. After one person has told the truth and a lie, everyone on the team guesses which place is the real birthplace.
4. In the end, you can delete the "lies" from the map - and you have a beautiful map with the places of origin of the team, which you may even be able to save on your shared team page.