Retrospective

What it means

A retrospective is a regular team meeting at the end of a sprint or project to review what worked, what did not and what to change next time. It focuses not on the product but on how the team works together, its processes and its tools.

It is one of the five events of the Scrum framework and the core of continuous improvement in agile management. The idea is that the team learns from experience continually, not just at the end of a big project when it is too late to change anything.

A retrospective only works in a blame-free atmosphere. The aim is not to find culprits but to identify the causes of problems in processes and agree on small, concrete improvements. The principle is close to Japanese kaizen, improvement in small steps.

How it works in practice

A common format uses three questions: what went well, what did not, and what will we try differently. The team picks one to three improvements, assigns an owner and reviews at the next retrospective whether they helped. A long list without actions is pointless.

Retrospectives are not just for developers. An accounting team can hold one after the annual closing or tax return season: what caused delays, which documents were missing, how to communicate better with clients. The result is concrete changes for next year.

A facilitator who watches the time, involves everyone and keeps the atmosphere safe helps a lot. Remote teams use online tools with anonymous cards that make it easier for quieter members to speak up.

What to watch out for

If agreed improvements are never implemented, retrospectives become an empty ritual and people stop speaking openly. It is essential to track actions and show that the team's suggestions have a real effect.

The presence of a manager who assesses performance can stifle honesty. The team needs space to discuss problems, including those related to management, without fear of consequences; otherwise the real causes are never uncovered.