Join Certified Scrum Trainer® John McFadyen for a 12-part video series exploring the scrum event known as the sprint retrospective. Throughout the series, he’ll share tips and tricks for creating impactful, engaging, and effective sprint retrospectives for your teams.
The seventh tip for running a great sprint retrospective is using metaphors to simplify the conversation. McFadyen suggests using one of the retrospective games that help the team visually describe movement. Teams have used several options for years—a speedboat, sailboat, rocket ship, horses, or any other transportation metaphor you can imagine!
Using the speedboat example, you’ll ask the team, “What is driving our speedboat forward?” Give the team time to reflect and answer, initiating a meaningful conversation. The team will talk about things that are valuable to them, helping them move forward as a high-performing team.
The next question is, “What is helping the speedboat go faster?” The team may reference obstacles removed from the team’s way or process improvements that help them deliver work faster.
Then, the team will discuss what’s dragging them down. An excellent way to get into this conversation is to have team members draw their thoughts. This visualization activity is a great way to express what’s happening in a simple-to-understand way.
The fourth question is, “What’s dragging you down?” The team may draw anchors or friction, which are metaphors for what’s happening on the team.
The final conversation concerns what’s slowing you down as a team. What things are getting in your way? You can visualize a destination, like a harbor, and how the team is going to get there. You can also discuss what is happening around the direction you're traveling. If a team member feels happy, that person might draw the sun or the sky. Perhaps objects are swimming around the water, causing you to slow down. How do you get around them?
Remember, there are many options for fun retrospective activities using metaphors and drawing to visualize your journey. The critical thing to remember is that when you close the retrospective, you should get feedback to improve how you facilitate the next one.
Get the latest resources from Scrum Alliance delivered straight to your inbox
Subscribe