One way to do this is to add ‘what works’ to a wiki-based handbook for new members who join the team. 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. ![]() You could talk with the team about next steps - e.g. 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.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. SHARK - what’s an upcoming threat to the project or team that you need to keep an eye on? what’s circling around that no-one is talking about?.SUN - what acts like sunlight for the project or team? what kind of recognition have you received? what is making you feel good?.ANCHOR - what’s dragging things down? what’s slowing down the progress of the project or team? which burdens need to be addressed?.WIND - what’s the wind in the project or team’s sails? what’s gone, or is going well? what kind of support are you getting?. ![]() LAND - what’s your destination? where are you headed? what does success look like for the project or team?.With that in mind, let’s identify the main areas of the template: The thing to remember about this process is that the way that you carry out the planning using this canvas is as important as the outcome. In addition, this fun retrospective format can be handled by both beginners and experts.Goals: define what has gone well and could be improved Thanks to its adventurous imagery, the Sailboat retrospective idea is the perfect exercise to launch a new project or simply run a Sprint retrospective. The iceberg, however, illustrates the dangers that could stop your journey in a very abrupt way. Other frameworks like the Sailboat retrospective, the Rose, Bud, and Thorn retrospective, and Start, Stop and Continue retrospective are also commonly used. When you create a template you’ll work with four key quadrants. ![]() The anchor symbolizes things that can slow down the boat on its way. This retrospective template creates an easy-to-follow foundation for evaluating and improving your work. The wind represents all the things that will help your boat reach the island. Picture this! Your Agile team has turned into a sailboat crew, navigating the seas towards a paradise island. Connoisseurs know that the Sailboat retrospective template is what we call a Futurespective. This original activity will help the team project itself towards a common objective As for any retrospective session, the expected output is to develop an action plan by taking advantage of the knowledge accumulated during previous Sprints. What is the Sailboat Retrospective template Use the sailboat exercise to engage your team in the retro session and evaluate the previous sprint. The Sailboat retrospective is a very popular Agile retrospective technique.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |