It doesn't need to be a big change, it should just show the team that feedback is taken seriously and that retros are very useful. Just try to improve something in each and every sprint. It’s a good starting point for new teams who are not experienced with retrospectives. Sailboat Retrospective is a fun and easy way to boost the communication of what went well and what slowed the team during current sprint. The Quick Retrospective dives straight in, asking the team direct questions about the sprint: what was good and what was bad, then capturing ideas and actions from the team. Fun names like Boaty McBoatface often come up, a sign of a playful (perhaps a little chaotic. Define the team’s key focuses of attention. Ask teams to name their boat themselves, it can be a practical name or a fun one, the key is conversation to agree the theme/topic of the retrospective. It involves finding risks that threaten the success of your team. This retrospective technique uses a sailboat as a metaphor for the team. I am not saying that it is their favorite meeting, but all in all it leads to good discussions and (very important) improvements! Agree the topic/theme of the retrospective and name the boat accordingly. Iceberg (Rocks) One of the first steps of the sailboat retrospective is the iceberg or rocks.
![sailboat retrospective app sailboat retrospective app](http://sketchnote.me/wp-content/uploads/2019/06/speedboat-copie.png)
The retros became more interactive, there is more discussion, there are more notes on he board and the teams don't hate the retrospectives anymore. (note: Teams whiteboard contains a template for the sailboat)įor whatever reason retros based on those alternative are going way better. Collect feedback on your project milestones, organize and prioritize, and create and track actionable tasks to help. Team Retrospectives, a Microsoft Garage project is an extension for Azure DevOps that provides a first-class experience for retrospectives and general feedback board scenarios.
![sailboat retrospective app sailboat retrospective app](https://www.techagilist.com/wp-content/uploads/2019/07/Sailboat-768x576.png)
(as a matter of fact: that was actual feedback received during one of those 'keep, stop, try' session: "can we stop doing this? it is boring!")īased on that feedback I started searching for alternatives and found retros like: 'the sailboat', 'speed car' and 'hot air balloon'. Looking back is an essential part of moving forward. Mostly those meetings ended with just a few notes on the board and a team that was bored.
![sailboat retrospective app sailboat retrospective app](https://easyretro.io/_nuxt/img/sailboat.af54723.jpg)
What I noticed in my scrum teams is that the 'keep, stop, try'-like retrospectives are not being seen as inspiring and fun.