Sprint Retrospective
Also known as: Retro
The sprint retrospective is the last event of a sprint and the one focused on the team itself rather than the product. Having reviewed what it built in the sprint review, the team turns to how it built it: what practices, interactions, and tools helped or hindered, and what specific change would make the next sprint better. The output is not a long report but a short list of actionable improvements the team genuinely commits to trying.
The retrospective is what makes agile a system of continuous improvement rather than just a delivery cadence. Because it happens every sprint, problems are addressed while they are small and fresh, and improvements compound over time. Its effectiveness depends on psychological safety: people must feel able to raise what went wrong honestly, without blame, which is why skilled facilitation and a culture of trust matter so much. A retrospective that produces no change, or that people cannot speak candidly in, quickly becomes an empty ritual.
For HR and people leaders, the retrospective is a strong example of a practice worth borrowing beyond software. The habit of regularly, safely reflecting on how a team works — and committing to specific changes — applies directly to recruitment teams, onboarding processes, and any group that wants to improve deliberately rather than by accident. It also connects to how organisations think about learning and psychological safety, which are increasingly central to engagement and retention.
Frequently asked questions
What is a sprint retrospective?
A sprint retrospective is a meeting at the end of each sprint where the team reflects on how it worked — what went well, what did not, and what to improve — and commits to a few concrete changes for the next sprint. It focuses on the team’s way of working, not the product.
What is the difference between a sprint review and a retrospective?
A sprint review inspects the product — the increment built during the sprint — with stakeholders, while a retrospective inspects the process: how the team worked and what it will change. The review is about the what; the retrospective is about the how.
Why is psychological safety important in retrospectives?
Because a retrospective only works if people can raise problems honestly without fear of blame. Without that safety, the real issues stay hidden and the meeting produces no genuine improvement, becoming an empty ritual.
Can HR teams run retrospectives?
Yes. Regularly and safely reflecting on how a team works, then committing to specific changes, applies well beyond software — recruitment teams, onboarding processes, and any group that wants to improve deliberately can benefit from the practice.