The retrospective is a structured team meeting for reflection on process — not product. Typically held at the end of a sprint or iteration, the team asks: What went well? What could improve? What will we commit to changing? esther-derby and Diana Larsen published "Agile Retrospectives: Making Good Teams Great" (2006), which became the canonical guide to retrospective facilitation. The retrospective is arguably the most widely adopted Agile practice after the daily-standup.
Origins
The retrospective's intellectual roots are multiple. In scrum, the Sprint Retrospective (as the scrum-guide calls it) is a formal event; ken-schwaber and jeff-sutherland incorporated reflection as a structural requirement of the empirical process. In extreme-programming, reflection was embedded in kent-beck's emphasis on sustainable-pace — teams that burn out cannot improve. The practice also draws from organizational learning traditions: Argyris and Schon's double-loop learning, Deming's PDCA cycle (plan-do-check-act), and Japanese kaizen (continuous improvement).
Intellectual Contribution
The retrospective's insight is that process improvement cannot be outsourced to management consultants or quality departments — it must be done by the team doing the work, about the work they are doing. This is the organizational corollary of inspect-and-adapt: just as software is inspected and adapted at the sprint review, the process of building software is inspected and adapted at the retrospective.
esther-derby and Larsen gave the retrospective structure that transformed it from an open-ended conversation (which tends toward venting) into a productive working session. Their five-stage framework — set the stage, gather data, generate insights, decide what to do, close the retrospective — manages the dynamics of psychological safety, creative thinking, and commitment. psychological safety (a term from Amy Edmondson) is a prerequisite: teams that fear blame will not surface real problems.
The retrospective is also the primary vehicle for self-organizing-teams to exercise genuine autonomy over their process. An organization that mandates a retrospective format, restricts what can be raised, or ignores team commitments has undermined the practice's function while preserving its form — a characteristic dark-agile failure mode.
Significance
The retrospective's wide adoption reflects something real: teams consistently report value from structured reflection that they don't report from many other Agile ceremonies. Its intellectual contribution — making improvement the team's job, recurring and ritualized — transferred beyond software development into general management practice.
Related practices: daily-standup, sprint-review, sprint-planning.