The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. The cookie is used to store the user consent for the cookies in the category 'Performance'. This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category 'Other.

Sailboat Retrospective by Johanna Torstensson Miro, online. The cookies is used to store the user consent for the cookies in the category 'Necessary'. Inspired by this Agile/Scrum/Design Thinking approach Online. The Sailboat or Speedboat Method for Sprint Retrospectives is an easy way to: adopt, reflect and map the teams way forward easily, in a fun, tactile and visual. The Sailboat Retrospective helps to identify potential improvements. The nice thing about it: The Spotify Health Check Retrospective can be carried out in tribes (several teams) as well as in individual teams. This cookie is set by GDPR Cookie Consent plugin. Note that the purpose of the Sprint Retrospective is not yet achieved. The Spotify Health Check (based on the Spotify model) is one of the classics when it comes to frameworks to scale agile. The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category 'Functional'.

The cookie is used to store the user consent for the cookies in the category 'Analytics'. These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly. Try to improve a little each sprint instead of trying to bring big changes at once. A small action that brings a small improvements is already very good. With the sailboat retrospective technique, the team will identify things that helped the sprint move forward as well as what held it back. The template also includes wind, an anchor, and rocks, so you can outline what is helping your team, what is holding your team back, and any project risks, respectively. In this depiction, your team is the sailboat moving toward the island (your goal). Let’s talk about how your distributed team can run a successful remote retrospective. The sailboat technique provides a visual model to guide your retrospective. Remember: you will not always have big live changing action items in each retrospective. This can make your agile retrospectives particularly challenging. You want to have 1 – 2 action items at the end of the retrospective that you can implement in the next iteration(s). Do please like and subscribe if you find this video helpful Retrospective Sailing Example Case Study - workshop - sailboat retrospective. Don’t focus too much on external people or factors, but mainly on the things that are within the control of the team to identify improvement actions that the team is able to take. While having the discussion on a topic, always focus on what’s within the control of the team. It’s important that everything you are discussing in the “Helping us”, “Holding us back” and “Obstacles” categories are related to the overall goal that you are trying to achieve as a team.

After this, you can do a quick dot voting session to determine the most important one(s) and start with a discussion on those.įirst discuss all the post-its in the “Destination” category and come to a conclusion of the goal of the team before discussing the other stages. “Obstacles”: what risks do we see in the future, that could prevent us from reaching the goal? Something that we see happening, but is not yet happening to us today.Īfter explaining the stages to your team, give everybody a few minutes to write down their thoughts on a post-it.“Holding us back”: what is currently holding us back, slowing us down, or preventing us to reach our goal?.It helps teams to identify what went wrong, what. “Helping us”: what is currently helping us on our road to achieving this goal? What should we keep doing? A Sailboat Retrospective is a visual technique that helps you and your agile team to analyse the last sprint.The running time of this retrospective can vary.

What are we striving for? As mentioned above, this can be something related to the product that you are building, or it can be something related to the way of working within the team. This retrospective is typically used with Scrum teams but it works for any type of team looking for feedback. “Our destination”: what’s our goal? This should be the main theme for the retrospective.If (('cookieConsent=all') || sailboat retrospective consists of two rounds: Motivate team members to attend the event instead of having to coerce them into joining. Define a structure that keeps your next agile retrospective on track and effective. The speed boat Agile – An Effective Agile Retrospective Tool - Nutcache Achieve concrete goals and get to the root cause of problems your team faces.

Agile retrospective sailboat