![]() What is giving us wind in our sails to go to the island? What helps us move forward? The island represents the sprint goal of your team's last sprint. You can use the metaphor: "Is the sailboat heading in the right direction?" The island The sailboat represents the entire team and their processes sailing to their goal. It gives you, as the facilitator, the perfect starting point to communicate the exercise through metaphors. The sailboat, the sail, the anchor, the rocks, and the island (the focus point of the retrospective). The sailboat retrospective consists of five elements. Searching for risks they'll face, seeing what is working, looking for things that are slowing them down, and making sure the sailboat is heading in the right direction. Running the sailboat retrospective, you and your team are trying to find how to get the boat to smooth sailing. On the template, you can visualize the sprint goal as your focus point. The power of the sailboat retrospective is in the way you visualize everything from the previous sprint. These activities will become part of the team's core activities. These are activities or experiments that the team tried out and that are working! So before you start this exercise, you'll need to gather the activities that are not part of the current process. Keep into consideration the technical and behavioral elements. These activities hurt the team's performance. These are activities that the team faces that are wasting time for them or are inefficient. ![]() Where can they reduce waste using a new tool or communication method? These activities should positively impact the team and improve the team's performance. These are activities that the team helps become more efficient. This retrospective template is less structured than the lightning decision jam but is a great tool to guide the conversation in your team. The start-stop-continue sprint retrospective template consists of three columns. Being a new scrum master, this template was so straightforward the retrospective almost ran by itself! ![]() The start-stop-continue retrospective template is the first agile retrospective template I've used in my career. Take the top-right items and move them to the backlog. This can be a task that should be done or an enhancement of the definition of done. Take the top-left items and convert them to actionable tasks you'll do in the next sprint. Go for each idea over the effort for each idea.Īfterward, go over the impact of the ideas. Take the top 5 ideas and bring them over to the action board. Here you can use dot voting (or heatmap voting) to prioritize the ideas. Review the ideas on the board and group similar items together. It is time to post all of the ideas onto the whiteboard or flipchart. Give the team time to brainstorm ideas around the opportunity question. We take the opportunity question from the previous exercise and paste it onto a new whiteboard or flipchart. When the team voted, it's time to rewrite the problem statement into an opportunity question or 'How Might We'. You can use a double-layered voting strategy to prioritize the issues. Let the team members review the sticky notes on the bottom of the sailboat. They answer the following questions:Īfter a set amount of time, the team members stick up their anchors on the bottom side of the sailboat. The second question the team focuses on is the anchor. We ask them:Īfter they've written down their thoughts on a sticky note for each thought, each team member presents their sticky notes to the team. This is an icebreaker for the team members. We are only focussing on the anchor and using the sail as a warm-up exercise for the team. This sailboat has fewer features than when running the sailboat retrospective template. After this exercise, the team reviewed what was helping them move forward and what was holding them back. The sailboat is a straightforward exercise. It is structured so you'll always have actionable tasks for the next sprint at the end of the meeting. The sailboat, the 10-for-10 exercise, and the action board. The lightning decision jam consists of 3 phases. Writing their ideas and issues on (digital) sticky notes in silence. This exercise allows the team to get themselves heard-even the shy team members.ĭuring this retrospective meeting, each team member works alone together. I taught this template to my fellow scrum master, and he is using this template regularly in his scrum team. ![]() It is a versatile retrospective that can be used for many problem-solving meetings. The lightning decision jam is my favorite retrospective template. Here are my top 3 sprint retrospective formats I use in our agile team. The retrospective meeting can become one of those no one looks forward to. But using the same retrospective templates can become boring for your team members. After every sprint, preferably after the sprint review, most agile teams run a sprint retrospective.
0 Comments
Leave a Reply. |