How to Facilitate a Retrospective: A 60-Minute Agenda

Introduction

The quality of a retrospective depends as much on facilitation as it does on the template. A retrospective can easily become a status update, complaint session, or rushed action list.

This guide explains the approach in practical terms: what it is, why it is useful, when to use it, how to apply it step by step, and which mistakes to avoid.

What is it?

Retrospective facilitation is the process of guiding a team through reflection, interpretation, prioritization, and action without controlling the team's conclusions. The facilitator manages the structure, time, participation, and safety of the conversation.

Why is it useful?

A retrospective can easily become a status update, complaint session, or rushed action list. A clear agenda helps the team move from observations to shared understanding and then to a realistic commitment within a fixed amount of time.

Benefits

• Balanced participation instead of discussion dominated by a few voices.
• A predictable flow that reduces facilitation pressure.
• Focused use of time through grouping and voting.
• Higher action completion because ownership is explicit.

When should you use it?

Use this agenda for a team of roughly four to ten people after a one- or two-week sprint. Adjust the timing for larger teams, complex incidents, or sensitive topics that need more space.

How to do it

1. 0-5 minutes: Set the stage. State the goal, scope, timebox, and working agreement. Review whether the previous retrospective action was completed.
2. 5-15 minutes: Gather data. Give participants quiet time to add observations to the board. Avoid discussing each card as it appears.
3. 15-25 minutes: Group and clarify. Combine similar cards, ask neutral clarifying questions, and name the emerging themes.
4. 25-30 minutes: Vote. Give each participant a limited number of votes. Select one or two themes for deeper discussion.
5. 30-48 minutes: Generate insight. Explore causes, impact, patterns, and constraints. Keep the discussion on the system rather than personal blame.
6. 48-58 minutes: Decide actions. Define one or two specific actions with owner, deadline, and success signal. Use the final two minutes to check confidence and close.

Real example

A team used the agenda after three sprints of carryover. Cards initially blamed estimates, scope changes, and reviews. Grouping showed that most issues started when stories entered the sprint without a ready decision from design. The team chose one action: product and design would run a readiness check 48 hours before planning. The next retrospective reviewed whether carryover changed.

Common mistakes

• Explaining every step for too long and reducing reflection time.
• Discussing cards while people are still writing, which creates anchoring.
• Allowing the team to select five or more actions.
• Skipping the previous action review and weakening accountability.

FAQ

Should the Scrum Master always facilitate?

Not necessarily. Rotating facilitation can build team ownership, provided the facilitator understands the process and can remain neutral.

What if the team has more topics than time?

Use voting, record the remaining themes, and schedule separate problem-solving only when a topic is urgent.

How should the facilitator participate?

They may contribute observations, but should clearly separate that role from facilitation and avoid using authority to steer the conclusion.

Conclusion

A strong retrospective agenda protects four things: safety, equal input, focus, and follow-through. Keep the structure simple, let the team own the content, and finish with fewer, clearer actions.

Call To Action

Open a SprintsPlans board before the meeting, use anonymous voting to prioritize themes, and track the selected action through the next sprint.