When you recognize what went well in your previous efforts as a team, it’s easier to duplicate those results the next time.Ĥ. Winds help a sailboat gain speed.Ī good wind lets a sailboat achieve its top speed. 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.
![the sailboat retrospective the sailboat retrospective](https://www.techagilist.com/wp-content/uploads/2023/03/Sailboat-Retrospective-768x334.jpg)
![the sailboat retrospective the sailboat retrospective](https://media.nngroup.com/media/editor/2019/01/07/sailboat-retrospective.jpg)
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.
![the sailboat retrospective the sailboat retrospective](https://images.ctfassets.net/ede0ajjyowtx/63tAd4UxI4EIKmWYwisc44/d44ef3b423e30178e2c9b3e0cc8bf71c/zeilboot.png)
I like the tool called Miro to collaborate in the retrospective, you can find in the link below a template to run the sailboat retrospective.You’ll need to consider the progress you’ve made, what obstacles are in your way, and the goals you want to accomplish. Once you have all the information in the board it is time to group the similar feedback and discuss the most important topics and do not forget to create an action plan for the next sprint to keep the People, Process and Product always improving. Reef: Next month we going to need help from the US team to complete the system test so we have to plan this dependency in advance. Sun: My colleague John helped me to build a new library to process messages faster.Īnchor: We had issues deploying to the server causing delays to update the system. Wind: The Product Owner was very attentive to the sizing of the user stories and that helped us to delivery value faster. That is a very good way to bring the team to discuss about People, Process and Product bringing up ideas, problems and a bit of planning ahead. Using this technique we can get the team feedback in various aspects such was "The wind" what as good in the sprint, "The anchor" what was bad in the spring, "The Sun" shout out for the team, positive vibes and "The Reef" risks ahead.