![]() ![]() It’s a visual way for your team to identify what pushed the project forward, as well as what held it back. Having several posters for different retrospectives will allow for easy variation of your retrospectives. The sailboat retrospective is a retrospective technique where you and your agile team members will envision the last sprint as a sailboat. Besides, the poster can be conveniently drawn upon using whiteboard markers so it can be easily reused for a next time. If you want put some perspective in your retro to get some bearing for the next product increment you could try this or a similar approach. This also allowed some additional discussion about further development of basic implemented features. Then each team member would indicate what the product would contain and whether it would be feasible. Reaching land in a certain sprint would indicate a next version of the product. The reef represent future risks ahead, the anchors represent negative factors, such as delaying issues, the wind represents positive forces, such as things that worked well, while the anchors represent negative factors, and the land represents the goal or vision for the sprint. This allowed the team to indicate what they thought to expect the next few sprints and what route the boat would take before reaching land. Visualize the retrospective as a sailboat journey. So I decided to create a poster with a whiteboard film and adapt the sailboat retrospective to include sprint wave lines. Adding sprints to the mixīecause of the fact that we, as many other teams, had a deadline, I was searching for a way to get some perspective on where we were standing with regards to the goal we were trying to achieve. By the end of the discussion, I immediately saw that the simple act of extracting and discussing the goals provided the sailboat (the team) a strong wind helping it draw nearer to its destination. Each team member can add some of these items to the picture to indicate what factors they think are important. The sailboat retrospective lets the team have a an island representing the goal to reach, have the wind as external factors helping the team, anchors that hold the team back, and rocks as risks that the team would have to overcome. You could do this as part of the retrospective but I find it will be sloppy and I get nervous doing it in front of people.As I was asked to organise one of the retrospectives for our team I had a look at several retrospective types and found the sailboat retrospective that I thought could best be adapted for our team. This retrospective takes about 45 minutes Preparations You will need a big piece of paper or preferrably a whiteboard. This particular retrospective is a very visual way of finding our improvement actions. There will be another retrospective in a few weeks. Then, the retrospective uses certain imagery to help you review a recent sprint or project in a creative way. ![]() It starts with imagining your team as a sailboat embarking on a journey. Small, concrete actions are preferred before large lofty goals that we don’t reach anytime soon. A sailboat retrospective meeting is a creative and engaging team exercise designed to promote open dialogue, collaboration, and problem-solving within a group. The purpose of this, and every retrospective, is to help us to improve by coming up with a few concrete improvement actions that we can complete / test / do until the next retrospective. Factors that are causing the team to lag or to delay them to proceed further. Represents things that are helping the team to increase the flow. View the Project on GitHub appliedtechnology/retros Retrospective script - Sailboat Resulting objective of the team or the vision towards which the team is leading. Retrospectives used at School of Applied Technology ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |