Hi guys, in this post I will explain how can you use SailBoat exercise as a tool for a retrospective. I learned this exercise few years ago when I worked together with Vasco Duarte. Few weeks ago I saw an upgrade in Pedro Gustavo blog.This exercise can be found in the book: “Getting Value out of Agile Retrospectives”, a book written by me and Ben Linders with the foreword from Esther Derby. The book can be downloaded by free in LeanPub.com or InfoQ.com, please download it and spread it within your colleagues.
Here you can find my previous blog “Getting Value out of Agile Retrospectives: “High Performance Tree””.
What you can expect to get out of this technique
From my experience, this technique is quite appreciated by teams because of its simplicity. This exercise helps teams to define a vision where they want to go, it helps them to identify risks during their path and allows them to identify what slows them down and what actually helps them to achieve their objectives.
When you would use this technique
I believe this technique is quite simple and does not require any special occasion. Although, it might be interesting for situations when a retrospective is conducted with more than one team at the same time. I had a situation, not long time ago, that two teams worked together and because of their level of dependency on each other, they decided to conduct a common retrospective because of some ongoing issues. Using the SailBoat exercise can be extremely interesting, because we simply put the name of both teams on the SailBoat and we remind everyone that we are on the same SailBoat navigating to the same direction.
This technique reveals all good things and less positive things performed by a team.
The SailBoat exercise is suitable for any team, it does not require any specific level of maturity.
The islands represent teams´ goals/vision. They work everyday in order to achieve these islands. The rocks represent the risks they might encounter towards their vision. The anchor on the SailBoat is everything that is slowing them down on their journey. The clouds and the wind represents everything that is helping them to reach their goal.
Having the picture on the wall, write what is the team vision or what are goals as a team. After that, start a brain storming session with the team allowing them to dump their ideas within different areas. Give ten minutes to write their ideas. Afterwards, give 5 minutes to each person to read out loud their ideas.
At this point discuss together with the team how can they continue to practice what was written on the “clouds” area. These are good ideas that help the team and they need to continue with these ideas. Then spend some time discussing how can the team mitigate the risks that were identified. Finally, together with the team chose the most important issue that is slowing the team down. If you do not find an agreement within the team about the most important topic that should be tackled, you can use vote dots. At the end you can define what steps can be done in order to fix the problem and you can close the retrospective.
As many other exercises, this exercise does not require a collocation of a team. You can use, for example, tools like Lino, to apply the exercise on non-collocated teams. This tool allows us to do everything what we need in order to run this exercise.
What do you think? Your feedback is always extremely important for me, so please leave me your comments.
In case you are interested in Agile Retrospectives I am creating a 12 WEEK FREE AGILE RETROSPECTIVES PROGRAM. This is a complete self study program where you will learn anything that you need to become a great Agile Retrospectives facilitator, just click here to access it.