Scrum

What is Retrospective?

Q: What is Retrospective?

Retrospective is the Scrum event in which the team inspects its own process and decides what to improve in the next Sprint. It happens at the end of every Sprint, before the next Planning, with a timebox proportional to the Sprint length. It is the engine of continuous improvement: without retrospectives, the team keeps delivering more of the same — with the same problems — indefinitely.

Retrospective is the Scrum event in which the team inspects its own process and decides what to improve in the next Sprint. It happens at the end of every Sprint, before the next Planning, with a timebox proportional to the Sprint length. It is the engine of continuous improvement: without retrospectives, the team keeps delivering more of the same — with the same problems — indefinitely.

In practice

An effective retrospective is facilitated by the Scrum Master, lasts between 45 minutes and 3 hours, and follows an arc: create a safe space, gather data (what worked, what did not, what we learned), generate insights, decide on one or two concrete experiments and close with commitment. Formats vary — Starfish, Sailboat, 4Ls, Mad/Sad/Glad — but what matters is the outcome: specific actions, with an owner, that enter the next Sprint Backlog and are revisited. A well-run retro creates visible change in a few iterations. K21's A-CSM course goes deep on advanced retrospective facilitation.

What happens when it is missing

Without retrospectives, the team repeats the same problems Sprint after Sprint: the same unproductive meeting, the same blocked dependency, the same missing acceptance criteria. Frustration piles up, becomes hallway gossip, and ends in attrition. When the retro gets skipped "for lack of time", the team loses exactly the structured space that creates time — continuous improvement stops happening.