![retrospective sailboat method retrospective sailboat method](https://appliedtechnology.github.io/retros/sailboat.png)
Summarize the insights and action items that were identified during the meeting, and encourage team members to follow up on their commitments. Group similar or duplicate items and hold a vote to assign a priority to the changes. Decide on next stepsĬonduct a brainstorm on possible solutions or new ideas that can make the next sprint or project better based on the feedback from this retrospective. Identify strengths and areas for improvement. Ask questions to clarify and explore any areas of ambiguity. Look for patterns and themes in the data that emerges from the team's discussion. You might use prompts such as "What did we accomplish?" and "What could we have done differently?" Encourage everyone to contribute and avoid jumping to conclusions or blame.īy the end of this step, you should be able to answer the following questions: Invite team members to share their perspectives on what went well and what didn't during the project or iteration. This might include emphasizing the importance of open and honest communication, active listening, and respectful behavior. Kick off the retrospective meeting by explaining the purpose and any ground rules that the team should follow. Get the team warmed up and set the stage with a quick icebreaker and any necessary introductions.
![retrospective sailboat method retrospective sailboat method](https://images.prismic.io/whiteboards/b2d2f7cb-4a05-402b-a4a6-17edc113d627_sailboat_cover.jpg)
We also recommend having an impartial facilitator to help keep the retrospective on task, allow for better collaboration among the key stakeholders, and record insights.
![retrospective sailboat method retrospective sailboat method](https://media.nngroup.com/media/editor/2019/01/07/sailboat-retrospective.jpg)
You may not need to invite the entire team, just the main stakeholders involved the scope of the project or week sprint in question. Next, invite everyone that should be involved in the retrospective. If you’re conducting a remote retrospective, be sure to agree on which video conferencing tool (like Zoom) the team will use to communicate effectively. Even if you’re meeting in-person a digital collaboration platform like Mural is your best friend. Now, with increasingly hybrid and remote working environments, it’s not always possible to be in the same room. Traditional, in-person retrospectives usually involve a whiteboard, some post-it notes, and some markers in a meeting room. How to run effective retrospective meetings 1. Async retrospectiveĪ great remote retrospective option for distributed teams, conduct a retrospective asynchronously and reduce the number of meetings a team has to sit through. Use this framework to identify things as positive, negative, or having potential with the metaphor of a rose, its thorns, and a rosebud. Use a stoplight as a metaphor to consider and define what your team should start, stop, and continue doing. Sailboat retrospectives use a sailboat voyage as a memorable metaphor for the journey of completing a project or initiative from start to finish. Sailboat retrospectiveĪssess how well a project has been executed and identify areas for improvement.
![retrospective sailboat method retrospective sailboat method](https://cdn-cashy-static-assets.lucidchart.com/marketing/blog/2022Q2/the-value-of-making-project-roadblocks-visual/Speedboat-retrospective.png)
Though most often used by agile teams following the Agile methodology, the project retrospective is also helpful for any team looking to reflect on project progress and encourage continuous improvement. Reflect on a completed project and looks for opportunities to improve the way they work together in the future. There are many different types of retrospectives, but most of them make sure to touch on a few key points:Ī simple retrospective to understand what went well, what went poorly, what ideas the team has, and how to take action to make the next sprint or project better. Retrospectives are an essential part of continuous improvement and help teams to learn from their mistakes and make incremental improvements over time. The goal of sprint retrospective meetings is to identify areas of improvement and come up with action items to address them in future projects or iterations. Improve collaboration by fixing workflowsĭuring a retrospective meeting, the team members gather together to discuss and analyze the successes and failures of the project, the effectiveness of the team's communication and collaboration, and the overall process used to complete the work.Create a safe space for teams to voice feedback and raise concerns.Identify challenges or opportunities for improvement in real-time.Retrospectives have many benefits, including: The goal is to evaluate past performance to improve process efficiency, teamwork, workflows, interactions, and the team’s definition of done. Retrospectives (or ‘retros’) are held at the end of each project or sprint to reflect on what went well, what needs to improve, and what ideas may have potential. Retrospective meetings provide that structure. It’s essential to have an established framework for gathering and recording ideas, as well as a culture based on psychological safety, to ensure that your team feels comfortable giving honest feedback. When the projects and sprints are over, the work isn’t done.