A Retrospective is a ceremony held at the end of each iteration in an agile project. The general purpose is to allow the team, as a group, to evaluate its past working cycle. In addition, it’s an important moment to gather feedback on what went well and what did not. Finally, retrospective is a moment for the team to define actions that may fix or improve things identified as negative.

Sprint retrospective should take between 60 to 90 minutes for a two-week sprint and likely a bit longer (however, probably not proportionally longer) when doing longer sprints. Daily Retrospective should last between 10 - 15 minutes depending on the type of retro selected

The three common questions asked are, "What went well? What didnt go so well? What can we improve?" However there are many great retrospective ideas out in the Agile community, including variations and additions on the basic questions and creative facilitation techniques. We have a varied selection for you to choose from

Identify how to improve teamwork by reflecting on what worked, what didn’t, and why. We recommend running a Retrospective with your team every couple of weeks or at the end of a project milestone.

Start the retrospective by creating a new session. Give it a suggestive title and choose between different types of Retro you would like to run.

Let your team know the following at the start of the meeting: The reason you’re taking the time to talk about how we have worked is to see how we can make improvements. We’re coming into this meeting understanding that everyone did the best that they could given their knowledge and tools. This meeting is a safe space. Nothing that is shared will be used against anyone. We’re here to explore, not to blame.

Have the team think back over the chosen time period. What were the key events that occured? Provide a few examples, such as goals met, team celebrations, team members joining, company events. Anchoring the team in key milestones jogs the team’s memory of events that occurred and how they felt about them.

Depending on the type pf Retro you will run. explain to the team the meaning of all columns. Using our tool, have each team member write down by adding a new card what the team did well, one idea per note. Delete similar or duplicate ideas. Discuss each one briefly as a team.

Have everyone write down what they think can be improved, one idea per card. Delete similar or duplicate ideas. Discuss each one briefly as a team.

Have everyone brainstorm actions that can be taken to improve problem areas, one idea per card. Each person will have a few minutes to share their plan. Use the actions list to capture each action. Make sure to include who will do it, what they are doing, and by when.

Commit to when you’ll track progress on actions on a regular basis, such as at team meetings or at the next Retro.