Accordingly, the team can get a sense of which area had the biggest potential impact on the project. That team member can spot patterns and relationships between the group’s insights. Spend five minutes each taking turns to dig deeper into the insights recorded on each sticky note.Ĭhoose one team member to group similarly-worded insights together. Present your reflections in pairs or small groups. Use Miro’s Countdown Timer to keep things on track. Ask them to record their thoughts and reflections relevant to each area of the retrospective. Give everyone 10 minutes to create their own sticky notes. Like a sailboat, a sprint also has factors that slow it down, and risks in the face of a goal, target, or purpose to reach.Īsk each team member to write and reflect individually. Then, tie the visual metaphor back to how to run an Agile sprint. Explain the four components, and feel free to frame them as questions (for example, “what helps us work to move forward?”, “what held us back?”, “what risks do you see in our future?”, “what made us feel good?”). For some teammates, this may be the first time they’ve heard the analogy. Introduce the sailboat metaphor to your team. Get started by selecting the Sailboat Retrospective Template, then take the following steps to make one of your own. Running your own sailboat retrospective is easy, and Miro’s collaborative workspace is the perfect canvas on which to perform the exercise. To run a successful sailboat retrospective meeting, use Meeting mode to lead your team through each frame, set a timer for each section of the template, and control what participants can do on the board.
The metaphor of a sailboat gliding over water can help team members think about their work as it relates to the overall course of the project, and the ready-made template makes it easy to fill in and add stickies with ideas and feedback. When facilitating your team’s retrospective, this template is an easy way for everyone to jot down ideas in a structured manner.
Benefits of the Sailboat Retrospective Template Use this template at the end of your sprint to assess what went well and could have been done better. Everyone describes where they want to go together by figuring out what slows them down and helps them reach their future goals. The Sailboat Retrospective Template helps you organize this Agile ritual with a sailboat metaphor. If you are part of an Agile team, you know retrospectives are fundamental to improving your sprint efficiency and getting the best out of your team. When to use a Sailboat Retrospective Template? Sun - what went well, what made the team feel goodīy reflecting on and defining these areas, you’ll be able to work out what you’re doing well and what you need to improve on for the next sprint. Wind - what helped the team move forward, represents the team’s strengths Rocks - represent risks and potential blockersĪnchors - represent issues slowing down the team Originally based on the Speedboat retrospective by Luke Hohmann, the exercise centers around a sailboat as a metaphor for the overall project, with various elements broken down: The Sailboat Retrospective (also known as the Sailboat Agile Exercise) is a low-pressure way for teams to reflect on how they handled a project.
This Sailboat Retrospective template, created by Agile coach Johanna Torstensson, is a fun and visual way to talk through each of those things in an organized and impactful way.About the Sailboat Retrospective Template Simply asking teams to reflect on their work together is broad, and it can leave people feeling directionless. Understand what’s pushing you forward and what’s holding you back with the Sailboat Retrospective That’s why we’ve rounded up our favorite Miro retrospective templates to get you started – regardless of what type of team you’re part of. It’s a chance for them to reflect, connect, and ultimately improve.īut to reap the benefits of a team retro, you need to be prepared to run one effectively. But in reality, a retrospective is a valuable meeting for any type of team or project.ĭuring a retrospective, a team comes together to discuss their work and identify ways to better their processes, communication, relationships, and output as they move forward. A retrospective might feel like something that’s exclusive to product teams.