![]() ![]() ![]() This Sailboat Retrospective template, created by Agile coach Johanna Torstensson, is a fun and visual way to talk through each of those things in an organized and impactful way. Simply asking teams to reflect on their work together is broad, and it can leave people feeling directionless. Wind and clouds the things that helped the team propel forward. Anchors things that held the team back from making progress. Understand what’s pushing you forward and what’s holding you back with the Sailboat Retrospective The sailboat retrospective compares the sprint to a sailboat, getting the team to compare the things that affected the sprint to what propels a sailboat forward or backwards. That’s why we’ve rounded up our favorite Miro retrospective templates to get you started – regardless of what type of team you’re part of. The sailboat retrospective compares the sprint to a sailboat, getting the team to compare the things that affected the sprint to what propels a sailboat forward or backwards. It’s a chance for them to reflect, connect, and ultimately improve.īut to reap the benefits of a team retro, you need to be prepared to run one effectively. But in reality, a retrospective is a valuable meeting for any type of team or project.ĭuring a retrospective, a team comes together to discuss their work and identify ways to better their processes, communication, relationships, and output as they move forward. ![]() It uses this metaphor to help the people reflect on the last sprint, in order to determine the best way to navigate going forward. What created major bottlenecks or challenges? What has prevented your agile team from making as much progress as possible?īy the way, the Speedboat and Pirateboat Retrospectives are extremely similar to the Sailboat Retrospective and aim for the same goal.A retrospective might feel like something that’s exclusive to product teams. This agile retrospective technique turns your team into the crew of a sailboat travelling to its final destination: a sunny island. Anchor (decelerating obstacles)Īn anchor is the perfect representation of the things that have slowed down your sprint. These can persist for a long time if your team doesn't find a way to tackle them. A distributed retrospective is simply a retrospective conducted by a remote team. The rocks represent a potential risk or obstacle to your sprint. In this framework, it symbolizes everything that accelerated the team to achieve the goal faster in this sprint. It can contain both long-term and short-term goals for the agile team. The land or island is the boat's destination and thus a wonderful visual representation of the sprint goal. The 4 areas of the metaphor in detail: Island / Land (the goal) The sailboat retrospective is a retrospective technique where you and your agile team members will envision the last sprint as a sailboat. This format digs deeper, challenging teams to figure out what benefits and harms their project, timeline, and cooperation. Moreover, many retrospective techniques primarily look at what went well during a sprint and what didn't. The reef represent future risks ahead, the anchors represent negative factors, such as delaying issues, the wind represents positive forces, such as things that worked well, while the anchors represent negative factors, and the land represents the goal or vision for the sprint. A team does not need to be well-versed in agile concepts and terminologies to understand how this technique works for them. Visualize the retrospective as a sailboat journey. The use of the sailboat metaphor makes it much more accessible and digestible. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |