Agile retrospectives are structured team meetings held at the end of a sprint or project phase where teams reflect on what happened, identify improvements, and commit to actionable changes for the next iteration. Originating from the Scrum framework but now used across all Agile methodologies, retrospectives embody the principle of continuous improvement — they're the engine that turns experience into learning and learning into better performance. The Prime Directive, introduced by Norm Kerth, sets the psychological foundation: "Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand." Without this assumption of good intent, retrospectives devolve into blame sessions rather than growth opportunities. When done well, retrospectives create a safe space where teams surface uncomfortable truths, celebrate wins, experiment with new ways of working, and build the trust and adaptability that separates high-performing teams from the rest.
What This Cheat Sheet Covers
This topic spans 10 focused tables and 101 indexed concepts, 85 flashcards. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
A jump-to index of every table row in this cheat sheet.
An interactive map of every table and concept in this topic.
Table 1: Foundational Principles and Purpose
Retrospectives succeed or fail based on their foundation — the principles that guide how teams approach reflection and the clarity of purpose behind each session. These core concepts ensure retrospectives remain productive rather than perfunctory.
| Principle | Example | Description | |
|---|---|---|---|
"Regardless of what we discover, we understand and truly believe that everyone did the best job they could..." | • Foundational assumption of good intent that prevents blame and creates psychological safety • typically read aloud at the start of every retrospective to set a collaborative mindset | ||
After each sprint, team identifies 1-2 actions to improve velocity or quality | • Kaizen philosophy applied to team processes • retrospectives are the primary mechanism for inspect-and-adapt cycles that incrementally enhance how teams work | ||
Team members can raise process failures without fear of retribution | • Trust-based environment where people speak candidly about problems • without it, retrospectives surface only shallow issues while real blockers remain hidden | ||
"Reduce meeting interruptions" becomes "Team will use Slack status 'Focus Time' 9-11am daily" | • Retrospectives must produce specific, assigned, time-bound actions with clear owners • vague intentions like "communicate better" rarely lead to change | ||
45-minute retrospective for a 1-week sprint; 3 hours maximum for a 4-week sprint | • Fixed duration proportional to sprint length prevents retrospectives from dragging or feeling rushed • forces prioritization of most important topics | ||
Scrum Master guides discussion without dominating it | • Neutral guide role that ensures equal participation, keeps discussion focused, and helps team reach decisions • facilitator manages process, team owns content | ||
Rotate between Start-Stop-Continue, Mad-Sad-Glad, Sailboat formats across sprints | • Format diversity combats retrospective fatigue • different structures reveal different insights and keep team engaged rather than robotically filling same columns every sprint | ||
Review sprint burndown, velocity, bug count, cycle time before discussing feelings | • Objective metrics ground discussion in reality rather than subjective impressions • balance quantitative data with qualitative team sentiment | ||
All team members, product owner, and Scrum Master attend; stakeholders may join meta-retrospectives | • Inclusive attendance ensures all perspectives are heard • silent members often hold critical insights that loud voices miss | ||
Retrospective at the end of every sprint (1-4 weeks) | • Consistent rhythm establishes retrospectives as non-negotiable team ritual • skipping them signals process improvement isn't valued |