GuideRolesEventsWorkflow

LeSS Events

Retrospectives

LeSS has two levels of retrospective: Team Retrospectives (standard Scrum, per team) and the Overall Retrospective (unique to LeSS). The Overall Retrospective addresses cross-team and systemic issues that individual teams cannot solve alone.

Team + Overall · Timebox: Team: ≤1.5hr / Overall: ≤1.5hr

Overview

LeSS has two levels of retrospective: Team Retrospectives (standard Scrum, per team) and the Overall Retrospective (unique to LeSS). The Overall Retrospective addresses cross-team and systemic issues that individual teams cannot solve alone.

Event Ownership

Owned / Facilitated By
Scrum Master (facilitates both levels)
Facilitate Team Retrospectives per team using varied formats
Facilitate the Overall Retrospective with team representatives, PO, SMs, and managers (if any)
Ensure Team Retro improvement items are tracked and executed
Ensure Overall Retro systemic improvement items are owned and acted on

Who Should Be Present

Team Retrospective
Individual team members reflect on their Sprint. Standard Scrum retrospective focused on team-level improvements
Overall Retrospective
Team representatives, all SMs, PO, and managers (if any). Focuses on cross-team issues, organizational impediments, and systemic improvements

Preparation Checklist

01SM: Select retrospective format appropriate to each team’s situation
02SM: Gather Sprint data for each team and cross-team metrics for Overall Retro
03SM: Review prior retro actions and completion status
04Team representatives: Bring insights from Team Retros that need systemic attention

Facilitation Techniques

Click any technique to expand details and learn when to apply it.

Team Retro → Overall Retro Flow

Team Retros happen first. Each team identifies issues they can’t solve alone. Team representatives bring these to the Overall Retro. This creates a natural bottom-up improvement pipeline.

Click to expand

Systems Thinking in Overall Retro

Use causal loop diagrams or system modeling to understand why systemic issues persist. This prevents treating symptoms and drives root-cause organizational change.

Click to expand

Management Participation in Overall Retro

If managers exist, they attend the Overall Retro not to direct but to listen and commit to removing organizational impediments. Their role is to improve the system, not control the teams.

Click to expand

Tips & Tricks

01
Team Retros happen first, then the Overall Retro — bottom-up intelligence feeds systemic improvement
02
The Overall Retro is where LeSS organizations address structural and cultural issues
03
Managers attend the Overall Retro to listen and commit to action, not to evaluate teams
04
Limit improvements to 1–3 items at each level. Fewer committed actions produce more actual change
05
Vary retrospective formats every 2–3 Sprints to prevent retro fatigue
06
Systemic Improvement Tracking
Track Overall Retro improvement items in a visible backlog with owners, due dates, and status. Review at the start of every Overall Retro. Stale items signal leadership disengagement.
07
Organizational Experiments
Frame Overall Retro improvements as experiments: ‘If we try X, we expect Y.’ Run for one Sprint, then inspect results. This creates a culture of empirical organizational change.

Success Takeaways by Role

What each participant should walk away with when this event is run well.

Teams

Concrete improvement actions owned by team members; feeling heard on systemic issues

Scrum Masters

Deep insight into team health; systemic improvement items to champion with management

Product Owner

Understanding of process constraints affecting delivery; input on product-level improvements

Management (if present)

Direct insight into systemic impediments; commitment to organizational changes

Goal

Team Retros: Identify and commit to team-level improvements

Goal

Overall Retro: Identify and commit to cross-team and organizational improvements

Goal

Address systemic issues that individual teams cannot resolve alone

Goal

Celebrate successes at both team and product levels

Cross-Framework Definition
See Sprint Retrospective in the glossary
→