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. 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. 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.
SAILBOAT RETROSPECTIVE UPDATE
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.
SAILBOAT RETROSPECTIVE DOWNLOAD
Get started with this template (Free) Use this template (Free) Or download as: Word. 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. The sailboat retrospective is a framework & metaphor to reflect and align the end of a sprint. One way to do this is to add ‘what works’ to a wiki-based handbook for new members who join the team.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. But don’t forget to talk as much about what is going well as what isn’t. ‘mitigating actions’ for the ANCHOR stickies, or ‘preventative measures’ for the SHARK stickies. This step requires your team to detach itself and view the project from a bigger perspective. It involves finding risks that threaten the success of your team. Iceberg (Rocks) One of the first steps of the sailboat retrospective is the iceberg or rocks. You could talk with the team about next steps - e.g. The 4 steps to a sailboat retrospective 1. Once you’ve done all of this, it’s up to you what to do next. Go round each person asking what they notice or would like to call attention to. Talk about what you’ve all added to the template.When the rate of new sticky notes slows, give everyone 30 seconds longer.Spend some time ‘silent Jamboarding’ where everyone can place as many sticky notes on the template as they wish.
SAILBOAT RETROSPECTIVE HOW TO
Ensure that everyone knows how to use Jamboard by going through the basic controls.Create your own copy of the template and invite all members of your team to edit.Also, ANCHOR is about current problems, and SHARK is to do with future problems for the project or team. If it helps, consider WIND to be things internal to the project or team and SUN to be things external to it.
For example, the difference between WIND and SUN in this retro and the difference between ANCHOR and SHARK.