Reflect as a team on project goals, blockers, and future ambitions.
About the Sailboat Retrospective Template
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. 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:
Rocks - represent risks and potential blockers
Anchors - represent issues slowing down the team
Wind - what helped the team move forward, represents the team’s strengths
Sun - what went well, what made the team feel good
By 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.
When to use a Sailboat Retrospective Template?
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. The Sailboat Retrospective Template helps you organize this Agile ritual with a sailboat metaphor. Everyone describes where they want to go together by figuring out what slows them down and helps them reach their future goals.
Use this template at the end of your sprint to assess what went well and could have been done better.
Benefits of the Sailboat Retrospective Template
When facilitating your team’s retrospective, this template is an easy way for everyone to jot down ideas in a structured manner. 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.
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.
Create your own sailboat retrospective
Running your own sailboat retrospective is easy, and Miro’s collaborative workspace is the perfect canvas on which to perform the exercise. Get started by selecting the Sailboat Retrospective Template, then take the following steps to make one of your own.
Introduce the sailboat metaphor to your team. For some teammates, this may be the first time they’ve heard the analogy. 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?”). Then, tie the visual metaphor back to how to run an Agile sprint. 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.
Ask each team member to write and reflect individually. Give everyone 10 minutes to create their own sticky notes. Ask them to record their thoughts and reflections relevant to each area of the retrospective. Use Miro’s Countdown Timer to keep things on track.
Present your reflections in pairs or small groups. Spend five minutes each taking turns to dig deeper into the insights recorded on each sticky note.
Choose one team member to group similarly-worded insights together. That team member can spot patterns and relationships between the group’s insights. Accordingly, the team can get a sense of which area had the biggest potential impact on the project.
Vote as a team on what the critical issues are to focus on mitigating and developing. Use the Voting Plugin for Miro to decide what’s worth focusing time and effort on. Each person gets up to 10 votes and can allocate multiple votes to a single issue.
Diagnose issues and develop outcomes. Discuss as a team what your follow-up action plans are for maintaining or building on helpful behavior and resolving issues in preparation for future sprints. Add another frame to your board by clicking Add frame on the left menu bar and annotate your team’s insights and next steps.
Dive even deeper into how to make your own sailboat retrospective – and see examples – in our expert guide to making your own sailboat retrospective.
How do you conduct a sailboat retro?
When conducting a sailboat retro, make a space for you and your team to uncover valuable insights, some of which might not be shareable across your organization. For that reason, make sure to adjust your privacy board settings so that only you and your team can access it, and let them know this is a safe space to share ideas and feedback honestly. The Sailboat Retrospective Template is built for you to run your meeting session smoothly, having complete control of how participants can add to the board. Start explaining the concept of the sailboat retro methodology. If they don’t know it already, guide them through your meeting agenda and set the timer for each section. After the meeting, gather insights in another frame on the same board, and thank everyone for contributing to your retro.
DMAIC Analysis Template
Works best for:
Agile Methodology, Design Thinking, Operations
Processes might not seem like the funnest thing to dive into and examine, but wow can it pay off—a more efficient process can lead to serious cost savings and a better product. That’s what DMAIC analysis does. Developed as part of the Six Sigma initiative, DMAIC is a data-driven quality strategy for streamlining processes and resolving issues. The technique is broken into five fundamental steps that are followed in order: Define, Measure, Analyze, Improve, and Control.
User Story Map Template
Works best for:
Marketing, Desk Research, Mapping
Popularized by Jeff Patton in 2005, the user story mapping technique is an agile way to manage product backlogs. Whether you’re working alone or with a product team, you can leverage user story mapping to plan product releases. User story maps help teams stay focused on the business value and release features that customers care about. The framework helps to get a shared understanding for the cross-functional team of what needs to be done to satisfy customers' needs.
Lean Canvas Template
Works best for:
Agile Methodology, Strategic Planning, Agile Workflows
Business opportunities can get dense, cumbersome, and complex, and evaluating them can be a real challenge. Let a lean canvas streamline things and break down your business idea for you and your team. A great tool or entrepreneurs and emerging businesses, this one-page business model gives you an easy, high-level view of your idea — so you can stay focused on overall strategy, identify potential threats and opportunities, and brainstorm the various factors at play in determining your potential profitability in an industry.
Blue Ocean 4 Actions Framework Template
Works best for:
Leadership, Decision Making, Strategic Planning
For entrepreneurs, so much comes down to new users—how to attract them, impress them, and convert them to loyal customers. This template, designed by the authors of Blue Ocean Strategy: How to Create Uncontested Market Space and Make the Competition Irrelevant, will help you maximize value for you and your customers alike. Using the template’s four steps (divided into easy columns), you’ll easily evaluate your products in more innovative ways and make sure money is being spent in areas that really matter.
KWL Chart Template
Works best for:
Education, Brainstorming, Retrospectives
Sharing and learning new knowledge is the fuel in the tank of any ambitious team or organization. A KWL chart is a graphical organizer that powers the learning process. This easy template lets you design and use a KWL, with three columns: Know, Want to Know, and Learned. Then you and your team will fill in each column by following three steps: Take stock of what you know, document what you want to get out of your session, and finally, record what you’ve learned.
PI Planning Template
Works best for:
Agile Methodology, Strategic Planning, Software Development
PI planning stands for “program increment planning.” Part of a Scaled Agile Framework (SAFe), PI Planning helps teams strategize toward a shared vision. In a typical PI planning session, teams get together to review a program backlog, align cross-functionally, and decide on the next steps. Many teams carry out a PI planning event every 8 to 12 weeks, but you can customize your planning schedule to fit your needs. Use PI planning to break down features, identify risks, find dependencies, and decide which stories you’re going to develop.