1. Method Name

Retrospective

2. Alternative Names

Retro, Sprint Retrospective

3. Brief Description

A retrospective is a regular team meeting (typically at the end of a work cycle, e.g., a Scrum sprint), aimed at reflecting on what went well and what didn’t during the past period, and how the team can improve in the future. It is the driving force behind continuous improvement for agile teams.

4. Purpose / When to Use

It is used to improve teamwork, processes, and overall efficiency. It provides a safe space for the team to have an open and constructive discussion about how they work together. It is held regularly at the end of each sprint or iteration.

5. Procedure / How to Apply It

A good retrospective has 5 phases:
1. Set the Stage: Create a relaxed and safe atmosphere. Remind everyone of the “Prime Directive”: “No matter what we find out, we understand and believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation.”
2. Gather Data: Help the team recall what happened. Create a timeline of events; analyze metrics.
3. Generate Insights: Analyze why things happened the way they did. Look for patterns and causes.
4. Decide What to Do: Select the 1–3 most important issues and develop specific, measurable, and actionable steps to improve them in the next cycle.
5. Close the Retrospective: Summarize the results, thank the team, and agree on how you will track progress on the action items.

6. A Real-World Example

At the end of a two-week sprint, the Scrum team uses the "Mad, Sad, Glad" format. Each member writes on slips of paper what made them angry (Mad), sad (Sad), and happy (Glad) during the sprint. They then group the slips together and discuss the most common themes. They find that many of the slips fall into the “Mad” category due to frequent changes in requirements. They agree on a course of action: “In the next sprint, we’ll implement a ‘freeze’ on requirements after the first two days.”

7. Benefits

- Promotes a culture of continuous improvement (Kaizen).
- Improves team dynamics and communication
.- Empowers the team and gives it responsibility for improving its own processes
.- Addresses problems before they become chronic.

8. Risks / Limits

- It can turn into a blame game: If it isn’t well facilitated and there’s no sense of safety, people won’t be honest.
- Repetition and boredom: If the team keeps using the same format, retrospectives can lose their energy.
- No action: If the action items from the retrospective aren’t implemented, the team will lose motivation and trust in the process.
- Perceived as “psychotherapy”: The meeting can turn into a session of complaining without any effort to find concrete solutions.

9. Practical Tips

- Retrospective formats: There are dozens of formats for retrospectives (Starfish, 4Ls, Sailboat, etc.). Rotate them regularly to keep things fresh
.- A good facilitator is key: Ideally, this should be someone neutral (e.g., a Scrum Master) who guides the team through the process.
- Focus on the system, not the people: Look for flaws in the process, not in the people
.- Start and end on time: Respect the team’s time.