![]() Step 4: The work done, I ask the participants to post their anchors on the wall.Step 3: Then, individually or in small groups it is time to characterize the anchors (obstacles, constraints, things we don’t like).Step 3: Every team member gets several sticky notes. Step 2: At the beginning of the agile retrospective meeting the moderator should explain the meanings of the four L’s. Steps 1 & 2 After the opening and introduction of the game, I usually ask participants to work individually or in pairs (depending on group size) on the goal (desirable conditions) and the positive factors then to present their work to others. Step 1: Before the agile retrospective meeting starts the moderator should create and hang up four posters with the headers Liked, Lacked, Learned and Longed for.The green arrows represent positive elements that push our boat.The anchors represent the obstacles slowing the movement of our boat: impediments or things that our customers or users do not like about our product and affect its optimal functioning. The more they are low under the water, the more they are strong (well, up to you to follow this rule!).The boat position represents today and the distance between the boat and the island can be seen as an indicator (not in our case).Of course, the objective of the Speed boat (our product…) is to go fast (for best performance). So I first ask the participants to describe us precisely what characterizes the optimal performance, the desirable conditions (yellow notes attached to the port or on the island that the boat needs to reach).The boat is our system, our product, our project or our team, so name it (Here, the boat is our Agile transition team).Draw a speed boat on a whiteboard or poster.Rocks ahead – what risks/dangers are coming up?.Anchors – what is slowing down/dragging on the project ?. ![]() Sails – what is making the project faster/better ?.It’s essentially a visual collaboration game where you place issues around it to signify ![]() It is also fairly simple to understand, requires minimal preparation, and overall is a great introductory technique for teams unfamiliar with regular retrospectives.But whether you’re a fan of sailing or not, you may find the Sailboat Retrospective, a simple but effective Agile retrospective, extremely useful.įor those of you unfamiliar with this retro technique, there is a picture of a Sailboat. ![]() Do you like sailing?I like the Sailboat retro technique as it’s very good at gathering data and quickly grouping it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |