Retrospective (Agile)
The team's regular look in the mirror - what went well, what didn't, what to change next time. The ritual that turns experience into continuous improvement.
- Term
- Retrospective (agile)
- Is
- A recurring team-reflection meeting
- Asks
- What went well, what didn't, what to change
- Drives
- Continuous improvement
Forms & parts of speech
Definition in plain terms
A retrospective is a recurring meeting, central to agile ways of working, where a team pauses to reflect on how it has been working and how to improve.
Held typically at the end of each sprint or iteration, a retrospective asks the team to consider what went well (to keep doing), what didn't go well (to address), and what specific changes to make going forward.
The output is a small set of concrete actions the team commits to trying in the next cycle. The purpose is continuous improvement: rather than repeating the same mistakes, the team systematically learns from its own experience and adjusts.
A good retrospective is a safe, blameless space focused on the process and the system, not on blaming individuals, so the team can be honest about problems and improve how it works together over time.
Why it matters to growth leaders
The retrospective embodies a discipline every growth leader should value: regular, structured reflection that turns experience into improvement.
While it originated in agile software teams, the underlying habit - pausing to ask what's working, what isn't, and what to change, then committing to specific adjustments - applies directly to growth work.
Growth teams run experiments, campaigns, and initiatives constantly; without a retrospective habit, they repeat mistakes and fail to compound their learning.
A growth leader who builds regular retrospectives into the team's rhythm creates a culture of continuous improvement, where each cycle gets a little better and lessons are captured rather than lost.
The keys are the same as in agile: make it blameless and focused on the process so people are honest, and ensure it produces real changes rather than just venting. For a growth leader, the retrospective is a simple, powerful ritual for compounding a team's effectiveness over time.
At the end of each cycle, the team pauses to reflect together: what went well and should continue, what didn't and needs addressing, and what specific changes to make next time.
The leader runs it as a blameless space focused on the process and the system rather than blaming individuals, so people are honest about real problems.
The first retrospective surfaces a recurring handoff that keeps causing delays, and the team commits to a concrete fix - which they actually implement the next cycle, and the delays stop.
Over successive retrospectives, the habit compounds: each cycle the team captures lessons rather than losing them, and its effectiveness improves steadily.
The growth leader recognizes the retrospective as the engine of continuous improvement - the same discipline that makes agile teams better over time - applied to growth work.
By building regular, blameless, action-producing retrospectives into the team's rhythm, the leader turns the team's own experience into compounding improvement rather than repeated mistakes.
Synonyms & antonyms
Synonyms
Antonyms
Origin & history
The agile retrospective is the recurring reflection that drives continuous improvement - examining what worked, what didn't, and what to change; blameless and action-producing, it turns a team's experience into compounding gains.
Etymology: source.
Usage trends
Search interest for this term over the last five years:
Common questions
- What is an agile retrospective?
- A recurring meeting, typically at the end of each sprint, where a team reflects on what went well, what didn't, and what to change — turning experience into concrete improvements.
- What makes a retrospective effective?
- A safe, blameless focus on the process and system rather than blaming individuals, and producing a small set of real, committed-to changes rather than just venting.
- Why do retrospectives matter beyond engineering?
- The habit of regular structured reflection that drives continuous improvement applies to any team — including growth teams running constant experiments and campaigns — to capture lessons and avoid repeating mistakes.
Related tools & calculators
Resources & people to follow
- referenceWikipedia — agile retrospective
- referenceAgile and growth practice
- referenceRGM analysis — the retrospective compounds a team's effectiveness; keep it blameless and ensure it produces real changes, not venting
Curated, non-competitor resources verified per term.
Related training
Disciplines
Areas of marketing where retrospective (agile) is a core concern: