6 Retrospective Games (Scrum) for Successful 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 some cats. Instinctively, which one best fits the last sprint? The reasons for choosing a picture are relatively unimportant.
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 again in the later part of the retrospective.
5. Now we continue with the next phase of the retrospective, the "Data Gathering" (To the article: 5 Phases of a Retro are not enough). Alternatively, you can (for example in the Echometer Tool) also look together at the measures of the last retrospective.

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

1. First, explain the instruction: You will now roll two dice once for each team member. Depending on the number that comes up, you ask the respective team member one of the numbered questions.
2. To roll the dice, you can simply open the linked, free online dice game. This has two artificial dice. Optionally, you can of course also use real dice.
3. Either you define in advance an order in which team members are called upon. Or the dice are rolled first, the question is read out - and then the respective team member can decide who should answer this question.
4. Theoretically you can of course play 2 rounds of it.
5. Optional: A small riddle for the team: Which of the questions on the whiteboard above will never come up? 

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. What was great?
   2. What was confusing?
   3. What was exhausting?
   4. What was interesting?
2. Ideally, the feedback is initially 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 Gathering" can also happen 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 vote 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 series 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 change 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 you have 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.
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 to record more than 3 measures - focus on quality instead of quantity (more about 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 quickly. 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 early with stakeholders 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 appreciate 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 for themselves (if necessary on a digital whiteboard, see above). 
2. Timebox 5 minutes: Then the team member thinks of 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 last name is Rodriguez. I'm actually from Mexico, where I was born 39 years ago. My family moved to the U.S. 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 nice map with the team's places of origin, which you might even be able to save on your shared team page.