Keep the retrospective focused on finding solutions, not blaming individuals or criticizing past decisions.Follow up on the action items from the retrospective in the next meeting to ensure progress is being made.Make sure to assign ownership of these items and set clear deadlines. Based on the discussion, identify specific action items that the team can work on to improve.Data can help provide a more objective view of the team’s performance. Use data to help guide the retrospective discussion, such as team velocity or user feedback.Use these “winds” to define a desirable goal you will use as a true north for the rest of the retrospective.Ask the team to turn each anchor into goals, desires, or wishes and put them before the cloud to represent the gusts of wind pushing the boat forward.First collect all the anchors, as it’s easier for most teams to organize their current problems.Identify the Improvement Areas: The team discussed the negative factors and identified areas for improvement.They wrote these on the keel and the rocks, as the obstacles that slowed down the sailboat or could cause it to crash. List the Negative Factors: The team listed the negative factors that hindered their progress during the sprint, such as a lack of automated testing, dependency on external APIs, and unclear requirements.They wrote these on the sail and the mast, as the wind filled the sail and propelled the sailboat forward. List the Positive Factors: The team listed the positive factors that helped them during the sprint, such as good communication, pair programming, and code reviews.Write the Sprint Goal: The team wrote the sprint goal at the top of the sailboat: “Develop a mobile app with login, registration, and dashboard features.”.Draw a Sailboat: The team drew a sailboat with a sail, a mast, a keel, a waterline, wind, rocks, and a shore.Here’s how they conducted the Sailboat Retrospective: The team was able to deliver the features on time but faced some challenges during the sprint. Let’s take an example of a team that developed a mobile app during the sprint. And it’s definitely worth the time to help the team to build on this base. ![]() Note: The original Sailboat technique doesn’t have a Sun – I added it to give them a feeling of accomplishment as most teams should understand that there are already things that work just fine. Reef: Represent future obstacles that have been identified, which the group is likely to encounter in the subsequent iterations.Sun: What the team liked, the actions or attitudes that deserve thanks.Anchors: The things that held us back (Pirates, Rocks, Sharks, Icebergs, and Anchors).Sails: The things that helped us move forward (Wind, Cloud).Help propel the boat forward but obstacles such as pirates, rocks, and stubbornĪnchors represent the risks that the team might encounter that could slow themĭown or even stop them from getting to where they need to be. Towards their goal while dealing with winds and icebergs along the way. The idea is that the team is on a sailboat, heading ![]() It helps the team to reflect on what’s going well and what could be better, analyze their sails and anchors and identify opportunities for improvement or change. The Sailboat or Speedboat Method for Sprint Retrospectives is an easy way to: adopt, reflect and map the team’s way forward easily, in a fun, tactile and visual way. It’s called “Sailboat” because the metaphor of a sailboat helps the team visualize their journey, the obstacles they faced, and the direction they want to sail towards in the future. The Sailboat Retrospective is a fun and creative way for teams to reflect on the sprint and identify areas for improvement.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |