Wrap up: Make sure that the decisions and assignments made in the meeting are clearly documented and easily accessible for team members to reference.

Create action items: After root causes are identified, determine the actions you will use to resolve them and assign the action items to responsible team members who have the skills to complete the assignments.Generate insights: Analyze the data you’ve gathered to determine root causes of things that didn’t go as planned.Gather data: Discuss what happened in the last project and gather all of the ideas, opinions, and concerns from different perspectives.Set the stage: Create a safe space where participants can discuss positive and negative issues with the goal of finding solutions.Most successful retrospective meetings follow the same basic steps: The goal of all retrospective meetings is to improve processes and procedures. Different types of retrospective meetings These different perspectives can bring more clarity and insight as you develop an action plan to prevent future mishaps and to reinforce the things that are already working well. Including representatives from engineering, manufacturing, marketing, documentation, operations, and sales will give you various points of view. It is a chance to find areas that need improvement and to celebrate what went well. Instead, it should be a safe place where all team members can discuss the experience from their point of view.

The meeting is not meant to air grievances or to lay blame on others. The idea is to give everybody the chance to discuss what happened. It gives the team a chance to pause and objectively look at the work they did. Sometimes teams rush to the next project without taking time to reflect on the previous project first.Ī retrospective meeting encourages teams to capture lessons learned and is held shortly after a project is completed. In an Agile environment, teams are focused on developing and releasing quality products as quickly as possible.

Sailboat retrospective online