How often should retrospectives be held?

At minimum, at the end of every sprint (typically every 1-2 weeks). Some teams also hold retrospectives at the end of major milestones, after significant incidents, and at the end of projects. If a team is not holding regular retrospectives, they are missing their primary mechanism for continuous improvement.

What if the same issues keep coming up in retrospectives?

Recurring issues usually indicate that previous action items were not followed through, the root cause was not properly identified, or the issue is outside the team's control. Dig deeper into the root cause, escalate issues beyond the team's control, assign specific owners to action items with deadlines, and review action item completion at the start of each retrospective.

Should managers attend retrospectives?

It depends on the team culture and the manager's relationship with the team. If the manager's presence inhibits honest discussion, they should not attend. If the manager is a trusted participant who can act on systemic issues, their presence can be valuable. The key is that the retrospective remains a safe space for honest reflection. Some teams alternate between retros with and without management.

Book Free Assessment Calculator

Retrospective

Also known as:retrosprint retrospectivepost-mortemlessons learned

A regular team meeting at the end of each sprint or project phase where the team reflects on what went well, what could be improved, and commits to specific improvement actions.

In-Depth Explanation

A retrospective (or "retro") is a facilitated team reflection that drives continuous improvement. It is one of the most valuable Agile practices, providing a structured opportunity for teams to learn from their experiences and adapt their processes.

Retrospective structure (common format):

Set the stage: Create a safe environment, review the purpose
Gather data: Collect observations about the period being reviewed
Generate insights: Identify patterns and root causes
Decide what to do: Commit to specific improvement actions
Close: Summarise and express appreciation

Popular retrospective formats:

Start/Stop/Continue: What should we start, stop, and continue doing?
Mad/Sad/Glad: Categorise observations by emotion
4 L's: Liked, Learned, Lacked, Longed for
Sailboat: Wind (what helped), Anchor (what held us back), Rocks (risks ahead)
Timeline: Walk through the sprint chronologically, noting key events
Lean Coffee: Participants propose and vote on topics, discuss in priority order

Retrospective best practices:

Hold regularly (every sprint, or at minimum every month)
Create psychological safety (no blame, focus on systemic issues)
Involve the whole team (including remote members)
Vary the format to prevent staleness
Limit to 1-3 actionable improvements per retrospective
Track follow-through on committed actions
Keep time-boxed (60-90 minutes for a two-week sprint)
The Scrum Master or facilitator should not dominate discussion

Key principles:

"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." (Norman Kerth's Prime Directive)
Focus on systemic improvements, not individual behaviour
Actions should be specific, owned, and tracked

Business Context

Regular retrospectives create a culture of continuous improvement, where teams systematically identify and address process issues, leading to compounding efficiency gains over time.

How Clever Ops Uses This

Clever Ops facilitates retrospectives for all client projects and coaches Australian businesses on how to run effective retros independently. We believe that the retrospective is the single most important Agile practice because it drives all other improvements.

Example Use Case

"A team's retrospective identifies that code reviews are creating a bottleneck. They commit to implementing pair programming for complex features, which reduces review time by 50% in the following sprint."