Retrospective

A retrospective is a structured meeting where teams pause to reflect on how they work together. Rather than focusing on what they built, they examine how they built it: what practices helped, what hindered, and what should change. The retrospective creates space for continuous improvement, ensuring teams get better over time rather than repeating the same dysfunctions.

Why it matters

Teams that never reflect never improve. Problems become permanent. Frustrations accumulate. Good practices go unrecognized and fade. The retrospective provides regular intervals to surface these issues while they're still addressable.

Beyond process improvement, retrospectives build team health. They give everyone a voice, surface tensions constructively, and create shared ownership of how work happens. Teams that retrospect together develop stronger working relationships and greater psychological safety.

The practice embodies a growth mindset. Instead of treating processes as fixed or problems as inevitable, retrospectives assume everything can improve. This orientation keeps teams from accepting mediocrity.

Running a retrospective

While formats vary, effective retrospectives share common elements:

Set the stage. Create a safe space where people can speak honestly. Remind the team that retrospectives focus on systems and processes, not blame.

Gather data. Collect observations about the recent period. What happened? What stood out? Many formats structure this collection: what went well, what didn't, what puzzles us.

Generate insights. Move from observations to understanding. Why did things happen? What patterns emerge? What's causing recurring problems?

Decide what to do. Convert insights into action items. Be specific about who does what by when. Limit the number of actions to what's actually achievable.

Close. Thank participants, confirm action items, and check how the retrospective itself went.

Common formats

Different formats suit different contexts:

Start/Stop/Continue. Simple and accessible. What should we start doing? Stop doing? Keep doing?

Mad/Sad/Glad. Emotion-focused. What made you angry, disappointed, or happy? Works well for teams needing to process feelings.

4Ls: Liked/Learned/Lacked/Longed For. Comprehensive coverage of positive experiences, learning, gaps, and wishes.

Sailboat. Visual metaphor. What propelled us forward (wind)? What held us back (anchor)? What risks lie ahead (rocks)? What goal are we heading toward (island)?

Timeline. Reconstruct the iteration chronologically, adding emotions and observations at each point. Good for complex periods or incidents.

Starfish. Five categories: Start, Stop, Keep, More of, Less of. More nuanced than Start/Stop/Continue.

Rotating formats keeps retrospectives fresh and reveals different insights.

Common topics

Retrospectives surface familiar themes:

Communication. How well do team members share information? Are there gaps or redundancies?

Process. Are ceremonies valuable? Is the workflow efficient? Where are bottlenecks?

Tooling. Do tools help or hinder? What's missing or broken?

Quality. How are bugs, technical debt, and testing handled? What causes defects?

Collaboration. How well does the team work together? With stakeholders? With other teams?

Workload. Was the pace sustainable? Were estimates accurate? How was stress?

Making retrospectives effective

Several factors separate useful retrospectives from empty rituals:

Psychological safety. People must feel safe raising problems without fear of retaliation. Without safety, you'll hear only superficial observations.

Action follow-through. If retrospective actions never happen, people stop suggesting them. Track and complete action items visibly.

Facilitator neutrality. Having someone focused on process rather than content improves dynamics. This can rotate among team members.

Time investment. Rushing retrospectives produces shallow insights. Allocate sufficient time - typically one hour per two-week sprint.

Regular cadence. Retrospectives work best as rhythm, not response. Regular reflection catches small issues before they become big problems.

Variety. The same format every time gets stale. Vary the approach to surface different perspectives.

Anti-patterns to avoid

Common retrospective dysfunctions:

Blame sessions. Focusing on individual failures rather than systemic issues. Creates defensiveness and shuts down honest discussion.

Complaining without action. Venting feels good but changes nothing. Every complaint should lead to a proposed action.

Management hijacking. When leaders dominate discussion or turn retrospectives into status meetings, team voice disappears.

Action item amnesia. Forgetting what was agreed last time means repeating the same retrospective forever.

Superficiality. Discussing only easy topics while avoiding real problems. The uncomfortable topics are usually the important ones.

Skipping when busy. Canceling retrospectives under deadline pressure removes the mechanism for improving the conditions causing the pressure.

Beyond sprints

While retrospectives are standard in Scrum sprints, the practice applies more broadly:

Project retrospectives. At project completion, reflect on the entire arc. What would you do differently? What should future projects learn?

Incident retrospectives. After production problems, examine what happened and how to prevent recurrence.

Quarterly retrospectives. Bigger-picture reflection on team direction, growth, and satisfaction.

Personal retrospectives. Individual reflection on work patterns, skills, and goals.

The core practice - structured reflection leading to improvement - scales across contexts.

Tools like Klero can inform retrospectives by connecting team practices to customer outcomes. When teams see how their processes affect the product experience users have, retrospective discussions become grounded in impact rather than abstract preferences.