Purpose
The method helps clarify backlog, sprint work, and team flow concretely. It helps sort work by value, risk, and deliverability. The result is captured as a Sailboat Board, Risks, and Improvement Actions.
Agile
Sailboat Retrospective
Turns backlog, sprint work, and team flow into a tangible result by defining the destination island, collecting drivers and anchors, and agreeing on actions.
What moves the team toward the goal, what holds it back, what risks lie ahead, and which actions follow?
LowWorkshop45-90 min
How it works
The team follows the steps: define the destination island, collect wind and anchors, mark risks, cluster topics, and agree on actions. Each step is captured visibly. In the end, a Sailboat Board, Risks, and Improvement Actions are available so decisions, tests, or actions can follow directly.
Visual orientation
Method sketch for a quick mental model.
Flow
- 1Define destination island
- 2Collect wind and anchors
- 3Mark risks
- 4Cluster topics
- 5Agree on actions
The runsheet guides execution with 5 phases, timeboxes, 5 pitfalls, and clear stop criteria.
Open runsheetIdeal for
- Team Retrospectives
- Project Health Checks
- Workshop Engagement
Not good for
- Very short reviews
- Formal root-cause analysis
Deep dive
In detail
Sailboat Retrospective follows a clear working logic: define the destination island, collect wind and anchors, mark risks, cluster topics, and agree on actions. This turns the method into a visible thinking process instead of only a conversation. The participants move step by step from raw material, observations, or options to a shared structure. As a result, a Sailboat Board, Risks, and Improvement Actions support decisions, learning, and further planning.
Facilitation
Prepare a clear guiding question, the right information, and a visible workspace. Plan about 45 to 90 minutes with 4 to 12 people and use the format in a facilitated workshop. Keep facilitation lightweight; short timeboxes, visible intermediate results, and a parking lot for open questions are helpful.
Output artifacts
Sailboat BoardRisksImprovement Actions
Artifact templates
Sailboat Retrospective Working TemplateCompact working template for the Sailboat retrospective with winds, anchors, rocks, and next actions.canvas
Sailboat Retrospective Working TemplateCompact working template for the Sailboat retrospective with winds, anchors, rocks, and next actions.
canvassailboat-retrospective-working-template.md
Compact working template for the Sailboat retrospective with winds, anchors, rocks, and next actions.
Sailboat Retrospective Working Template
Goal
Use the sailboat metaphor to surface what moves the team forward and what holds it back.
Context
Which time frame or delivery should the team review?
Input
- Time frame:
- Team or group:
- Notes, signals, or examples:
Working area
- Destination island:
- Winds:
- Anchors:
- Rocks:
- Patterns:
Output artifacts
- Sailboat board:
- Risk list:
- Improvement actions:
Open questions
- ...
Decision / next step
Owner, date, and success signal.
When to choose differently
Short decision aid for existing alternatives.
Start Stop Continue
Statt Sailboat Retrospective, wenn ihr Teamarbeit, Backlog oder Retrospektiven in einem leichten Arbeitsformat organisieren wollt.
Similar methods
All methodsAgile
Start Stop Continue
Turns backlog, sprint work, and team flow into a tangible result by setting context and timeframe, collecting start ideas, and prioritizing actions.
Statt Sailboat Retrospective, wenn ihr Teamarbeit, Backlog oder Retrospektiven in einem leichten Arbeitsformat organisieren wollt.
Agile
Starfish Retrospective
Turns backlog, sprint work, and team flow into a tangible result by explaining five categories, collecting inputs, and formulating experiments.
Agile
4Ls Retrospective
Turns backlog, sprint work, and team flow into a tangible result by setting the timeframe, collecting liked and learned items, and selecting actions.
Agile
Mad Sad Glad
Turns backlog, sprint work, and team flow into a tangible result by defining the timeframe, collecting signals of mad, sad, and glad, and deriving patterns and actions.
Agile
Working Agreements
Turns team flow, expectations, and delivery rhythm into a tangible result by clarifying work context, collecting expectations, and setting a review cadence.
Agile
Sprint Retrospective
Turns sprint backlog, sprint execution, and team flow into a tangible result through reflecting on the sprint, collecting positives and challenges, and carrying actions into the next sprint.