You could do this as part of the retrospective but I find it will be sloppy and I get nervous doing it in front of people. This retrospective takes about 45 minutes Preparations You will need a big piece of paper or preferrably a whiteboard.
This particular retrospective is a very visual way of finding our improvement actions. Design thinking is an iterative problem-solving process that utilizes creative thinking to put the customer at the heart of everything a business does. There will be another retrospective in a few weeks. The Sailboat Retrospective is a design thinking tool that helps teams to navigate towards their goals while identifying the strengths and bottlenecks that they may encounter on their journey. Small, concrete actions are preferred before large lofty goals that we don’t reach anytime soon. The purpose of this, and every retrospective, is to help us to improve by coming up with a few concrete improvement actions that we can complete / test / do until the next retrospective. You and your team will discuss what you liked about the project or sprint, what you loathed, what you lacked (or longed for), and, most importantly, what you learned. View the Project on GitHub appliedtechnology/retros Retrospective script - Sailboat Much like start, stop, continue, this technique is pretty self-explanatory. I like the tool called Miro to collaborate in the retrospective, you can find in the link below a template to run the sailboat retrospective.Retrospectives used at School of Applied Technology The Sailboat retrospective template is great for teams who like to visualize their sprint reflections. Once you have all the information in the board it is time to group the similar feedback and discuss the most important topics and do not forget to create an action plan for the next sprint to keep the People, Process and Product always improving. It is also fairly simple to understand, requires minimal preparation, and. Wind represents something that pushes us forwards.
Anchor represents obstacles that have got in our way. A sailboat retro takes the following structure: Boat represents the team. A futurespective usually covers a wider range of time than a retrospective. The board is divided into three main parts: (1) introduction, (2) sailboat retro and (3) action items. Reef: Next month we going to need help from the US team to complete the system test so we have to plan this dependency in advance. Do you like sailingI like the Sailboat retro technique as it’s very good at gathering data and quickly grouping it. A retrospective looks back at events that have already happened, whereas a futurespective looks ahead to a future goal and what stands in the way. Sun: My colleague John helped me to build a new library to process messages faster.Īnchor: We had issues deploying to the server causing delays to update the system. Wind: The Product Owner was very attentive to the sizing of the user stories and that helped us to delivery value faster. That is a very good way to bring the team to discuss about People, Process and Product bringing up ideas, problems and a bit of planning ahead. Using this technique we can get the team feedback in various aspects such was "The wind" what as good in the sprint, "The anchor" what was bad in the spring, "The Sun" shout out for the team, positive vibes and "The Reef" risks ahead.