Agile sailboat retrospective3/24/2024 It is important to carefully reflect your last sprint and try to find out at which point you could have worked faster/ better/ more smoothly. Which aspects of our daily work are slowing us down?.What did we always want to do but didn’t dare to?.This is because they aren’t things that potentially harm your collaboration but are slowing you down or keep you from trying out new ways of work. What’s the difference to Rocks (risks)? Aspects in your collaboration that are holding you back are different to risks and therefore need to be looked at separately. This category contains factors that were holding you back in your last sprint. Sailboat Retrospective – Anchor (holding back) That’s how you can integrate your best practices in your agile collaboration.īy the way: If you like this retro format, you can open it directly in the team development tool Echometer: What propels us forward to reach our goals?īy identifying the pushing and positive factors of your agile collaboration you’ll learn to reflect your working behaviours more intensively and get an awareness of how you can work optimally.What makes us perform in the best possible way?.To figure out what those factors are for your fellow members, ask them questions like: This can be seen as a metaphor for teams: What makes a team go forward? In this agile retrospective technique the wind can be seen as all the pushing factors that make your team work efficiently. Or if you want to do it in a more metaphorical way: Which rocks did we have to avoid?īy reflecting this you can avoid risks in the next sprint and work more smoothly and solution oriented.Īs probably everyone knows, a sailboat needs wind to sail.To initiate the train of thought you can ask questions like: Rocks in the Sailboat Retrospective represent the risks and potential problems that occurred throughout the last sprint. Questions to open up a Sailboat Retrospective To give you a more detailed insight into what the different categories mean, we’ll provide you with examples on questions that can be asked. In the end you can use dot-voting to decide which topics you want to discuss more intensively.Īs you can see, it is fairly easy to do this. You should set a timebox of about five minutes for it. Afterwards the team members are asked to label sticky notes with topics that they want to discuss in each of the categories. You draw a sailboat, clouds, rocks, an anchor and an island on the flip chart and explain to your team which item represents which category. If you’re not good at drawing you can use pictures as well. In order to carry it out you need a flip chart, pens and sticky notes. Teams often appreciate this agile retrospective technique because it’s simple and clear. The Sailboat Retrospective is an agile retrospective technique which aims to define a vision where a team wants to go and the possible assistance and problems that may arise. So, the question is, how can you reach the desired island by implementing the Sailboat Retrospective? These four stand for different things which can possibly occur throughout a sprint: Rocks (risks), Wind (pushing), Anchor (holding back) and Island (goal). Everything you need for the perfect day on a boat, right? These are called Rocks, Wind, Anchor and Island. The Sailboat Retrospective contains four different categories that are used to discuss different elements of your agile collaboration. Still the Sailboat Retrospective is a great way to improve your agile collaboration and by using it you can definitely ease the waves on your way to success as a team. Wouldn’t you love it if your everyday work would feel like a day on a sailing boat? I definitely would, but unfortunately we can’t promise you the stars (or the ocean days) by asking you to try out agile retrospective techniques.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |