The sailboat retrospective model makes it easier to identify the significant challenges or bottlenecks that could be slowing you down.

You must also know what inhibits an agile team from pushing forward when the conditions are right to gain speed. There are times when you need to stand firm as a team during crisis situations. This tool works well when stormy weather hits, allowing the vessel to maintain its position while gaining resistance to capsizing.Įven a strong breeze won’t move the sailboat further if you throw an anchor during calm seas. Identifying these risks earlier in the journey makes it easier to avoid them.Īnchors are meant to keep a sailboat in the same spot. When your scrum starts breaking down, your team can face new obstacles because they’re not working together as efficiently. Even if the vessel survives, it could get hung up in that location. If a sailboat hits a rock, it could get damaged and sink. With the retrospective tool evolving to be a daily tool that agile teams can use to manage complications regularly, it’s crucial to know the four elements the method offers to encourage results. The original design was a team-building exercise that encouraged people to share creative ideas in a safe environment. In his book Innovation Games, Luke Hohmann introduced the idea behind the sailboat retrospective method. What Are the Four Elements of the Sailboat Retrospective Method? That’s why the sailboat retrospective method is a valuable template to follow whenever your agile team needs help visualizing the steps that lead to victory. If your calculations are off, even by a little, someone else can steal your victory at the last second. When your evaluations are accurate, you’ve got an excellent chance to win the race.

You’ll need to consider the progress you’ve made, what obstacles are in your way, and the goals you want to accomplish.

Sailboat agile retrospective