1/25/2024 0 Comments Sailboat retrospective examples![]() ![]() I like the tool called Miro to collaborate in the retrospective, you can find in the link below a template to run the sailboat retrospective. Once you have all the information in the board it is time to group the similar feedback and discuss the most important topics and do not forget to create an action plan for the next sprint to keep the People, Process and Product always improving. Reef: Next month we going to need help from the US team to complete the system test so we have to plan this dependency in advance. Sun: My colleague John helped me to build a new library to process messages faster.Īnchor: We had issues deploying to the server causing delays to update the system. From executive inputs to daily scrum meetings, this comprehensive visual guide navigates through critical processes involving teams, stakeholders, customers, and product owners. Group similar sticky notes and discuss (10 mins) Ask the team to start thinking about the current sprint. Start with asking the team to write what they think the overall team goal is, and place their sticky notes on the island. A lot of the time, you simply do not know where to begin or what to do. Introduce and explain the template to the team. Sailboat retrospective example and main components Weje template Working on different projects is not easy. Illuminate the agile scrum sprint retrospective framework with our compelling slide. How to run the sailboat retrospective Time needed: 60-75 minutes. Wind: The Product Owner was very attentive to the sizing of the user stories and that helped us to delivery value faster. Template 3: Agile Scrum Sprint Retrospective Framework. Here’s how they conducted the Sailboat Retrospective: Draw a Sailboat: The team drew a sailboat with a sail, a mast, a keel, a waterline, wind, rocks, and a shore. The team was able to deliver the features on time but faced some challenges during the sprint. Atlassian developed this retro template specifically for groups of 4-8 people to discuss what went well and what needs improvement, and to identify the next steps to take. Let’s take an example of a team that developed a mobile app during the sprint. ![]() That is a very good way to bring the team to discuss about People, Process and Product bringing up ideas, problems and a bit of planning ahead. We highlight these examples in Miroverse, and try to add our own examples there as well. Using this technique we can get the team feedback in various aspects such was "The wind" what as good in the sprint, "The anchor" what was bad in the spring, "The Sun" shout out for the team, positive vibes and "The Reef" risks ahead. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |