Sailboat Retrospective

Give your team a shared picture of its destination, momentum, obstacles, and risks—then choose a realistic improvement for the next sprint.

What Is a Sailboat Retrospective?

The Sailboat Retrospective is a visual Sprint Retrospective technique that represents the team as a boat traveling toward an island. Wind moves the boat forward, anchors slow it down, and rocks represent risks ahead. The picture gives people an approachable way to discuss goals, helpful forces, current obstacles, and future threats in one exercise.

Teams often use Sailboat when planning around an important goal, reviewing a complicated sprint, or looking beyond past events to upcoming risk. Identifying momentum and obstacles together creates a balanced conversation: the team can protect what helps, remove what slows progress, and prepare for what could disrupt the journey.

The Five Sailboat Elements

The Boat

The boat represents the Scrum team and its shared work. Its position encourages the team to consider current progress without judging individual performance.

The Island

The island is the destination: a sprint goal, product outcome, or better way of working the team wants to reach.

Deliver a major customer feature.
Improve customer satisfaction.
Reduce production defects.

The Wind

The wind captures forces that create momentum and should be protected or strengthened.

Strong teamwork and shared ownership.
Helpful build and test automation.
Effective communication and fast code reviews.

The Anchors

Anchors are present obstacles that slow the team or make progress harder.

Growing technical debt.
Manual deployment processes.
Unclear requirements and long approval cycles.

The Rocks

Rocks are visible risks the team may encounter if it does not prepare.

An upcoming fixed deadline.
Unresolved external dependencies.
Resource constraints or production risks.

Wind often resembles specific What Went Well examples, while anchors benefit from the neutral language used in constructive What Didn't Go Well examples. Rocks are different from anchors because they describe what may happen next rather than what is already slowing the team.

How to Run the Sailboat Exercise

Prepare the board. Create clearly labeled areas for the island, wind, anchors, and rocks, with the boat at the center.
Explain the picture. Connect every element to the team's shared journey and clarify the period or goal being reviewed.
Gather ideas. Give everyone quiet time to add specific observations before group discussion starts.
Group similar responses. Combine related cards while preserving meaningful differences between them.
Prioritize discussion. Identify the strongest wind to protect, the heaviest anchor to address, and the most important rock to prepare for.
Select improvement actions. Choose a small number of realistic actions, assign ownership, and agree when the team will review progress.

Review additional Sprint Retrospective examples for ways to write focused cards. Teams that prefer direct process prompts can compare Sailboat with the Start, Stop, Continue retrospective.

Facilitation and Discussion Tips

Review previous retrospective actions before creating new commitments.
Encourage every team member to contribute before prioritization begins.
Focus on improving systems and processes rather than assigning blame.
Celebrate positive momentum instead of rushing past the wind.
Address the largest obstacle first and keep action items realistic.
Ask what evidence would show that an anchor became lighter or a risk was reduced.

The guidance in Sprint Retrospective best practices supports psychological safety and follow-through. A brief retrospective icebreaker can help participants engage with the metaphor, while remote retrospective practices ensure distributed team members have equal time to contribute.

When to Choose Sailboat

Sailboat works best when a team wants an engaging visual format, needs to connect current experience with a shared destination, or wants to discuss future risks alongside existing obstacles. For an intense sprint where emotions need direct attention, the Mad, Sad, Glad retrospective may create more useful space. Choose the format that best supports the conversation the team actually needs.

Chart a clearer course for your next sprint

Free. No account. No setup. Just a visual path from reflection to action.

Create Free Session