6 Cool Retrospective Games for Interactive Retros

1. As a moderator, you explain the rules to each team member: In front of you on the Echometer Whiteboard are some pictures of small children. Instinctively, which one fits the last sprint best? The reasons for choosing a picture are relatively irrelevant.
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 - laughing is of course allowed. At most, something interesting is written down to be used 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 from 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. Each team member searches the internet, for example via Google, for a GIF. It should subjectively fit the last sprint.
2. This GIF is posted on the Echometer Whiteboard and explained to the other team members. Ideally, the moderation specifies a concrete order.

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. Champagne: What should we celebrate?
   2. Coffee: What gives us energy?
   3. Water: What could use a little more flavor or could be optimized?
   4. Let's toast: Where could you use some support from other team members?
2. Ideally, 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 does not take too long. By the way: With Echometer, this part, the "Data Collection" can also be done 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 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 set 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 shown in the graphic. Now everyone is asked to explain the results:
   "How do you explain the highest approval from your personal point of view? 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 at this point yet.
7. Prioritization: Each team member has 3 digital points to vote. Now put the points where you see a need for improvement.
8. Discussion: Discuss the areas that received 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 on in order to get feedback as quickly as possible.

6. Every member of the development team participates appropriately 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: Every team member strives to keep promises.
11. Focus: We don't let ourselves be 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. 5 minute timebox: The team member then thinks of an explanation for both places as to 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 last name is Rodriguez. I'm originally 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 a person has told the truth and a lie, everyone on the team guesses which place is the real birthplace.
4. At the end, you can delete the "lies" from the map - and you have a beautiful map with the team's places of origin, which you might even be able to save on your shared team page.