![]() Examples of anchors in the team process include changing priorities, a slow review process, or a redistribution of resources that stalls out the team. Examples of ‘wind in our sails’ usually include instances of collaboration or efficient communication among team members.Īnchors are problems or inefficiencies during the Sprint that held you back from sailing at an optimal pace. ![]() It represents what went well during the Sprint and the practices you want to continue encouraging within the team in the future. The wind is what drives your boat forward and helps you reach the island. Typically, areas of conversation during a Sailboat retro fall under one of the following categories: The topics you discuss during a Sailboat retrospective are focused on keeping the journey smooth and analyzing the problems that make it more difficult. ![]() Imagine your team as the crew of a boat propelled by the wind and each Sprint is like a stage of the trip towards your goal of reaching the land you see ahead of you. The Sailboat is a fun way of doing retrospectives by looking at your work as part of a sea journey. It gives you the opportunity to inspect your process from the perspective of a crew sailing a boat headed toward an exotic island. If you have come to this conclusion yourself, why not spice things up occasionally with a different retrospective format like the Sailboat retro? Step 4: The work done, I ask the participants to post their anchors on the wall.Keeping your retros fun is vital for maintaining high team engagement in the long run and continuously improving your process.Step 3: Then, individually or in small groups it is time to characterize the anchors (obstacles, constraints, things we don’t like).Steps 1 & 2 After the opening and introduction of the game, I usually ask participants to work individually or in pairs (depending on group size) on the goal (desirable conditions) and the positive factors then to present their work to others.The green arrows represent positive elements that push our boat.The anchors represent the obstacles slowing the movement of our boat: impediments or things that our customers or users do not like about our product and affect its optimal functioning. The more they are low under the water, the more they are strong (well, up to you to follow this rule!).The boat position represents today and the distance between the boat and the island can be seen as an indicator (not in our case).Of course, the objective of the Speed boat (our product…) is to go fast (for best performance). So I first ask the participants to describe us precisely what characterizes the optimal performance, the desirable conditions (yellow notes attached to the port or on the island that the boat needs to reach).The boat is our system, our product, our project or our team, so name it (Here, the boat is our Agile transition team).Draw a speed boat on a whiteboard or poster.Rocks ahead – what risks/dangers are coming up?.Anchors – what is slowing down/dragging on the project ?.Sails – what is making the project faster/better ?.It’s essentially a visual collaboration game where you place issues around it to signify It is also fairly simple to understand, requires minimal preparation, and overall is a great introductory technique for teams unfamiliar with regular retrospectives.But whether you’re a fan of sailing or not, you may find the Sailboat Retrospective, a simple but effective Agile retrospective, extremely useful.įor those of you unfamiliar with this retro technique, there is a picture of a Sailboat. Do you like sailing?I like the Sailboat retro technique as it’s very good at gathering data and quickly grouping it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |