Less Retrospective Template
📄
💾 Downloadless_retrospective_template.md
Markdown • 17,914 bytes
---
title: "Less Retrospective Template"
methodology: "agile"
complexity: "advanced"
owner: "mirichard"
updated: "2026-09-19"
primary_principles: ["continuous-learning", "systems-thinking"]
secondary_principles: ["collaborative-leadership"]
principle_rationale: "Combines team and whole-product retrospectives to investigate cross-team causes and assign shared improvement actions."
---
# LeSS Retrospective Format Template
## When to Use
- When multiple LeSS teams need both team-level and whole-product improvement discussions.
- When cross-team causes require shared follow-up beyond one retrospective.
## When NOT to Use
- To collect lessons without assigning and revisiting improvement actions.
- Do not close an improvement solely because it was documented or assigned. See [Lessons archive](../../../../../../docs/principles/anti-patterns.md#lessons-archive).
## Pairs Well With
- [Sprint Retrospective Template](../../../../../../domains/team/templates/agile/sprint_retrospective_template.md).
- [Cross Team Coordination Template](../../../../../../domains/delivery/methodology-frameworks/agile-scrum/scaling-frameworks/less/cross_team_coordination_template.md).
Selection context: Team domain; agile methodology; advanced complexity. Match the situations above to project phase, risk, team size, and industry using the [decision-engine context model](../../../../../../meta/architecture-research/800-801-context-assessment-model.md).
Use one defined product, shared Product Backlog and integrated product outcome. Coordination techniques and agenda durations here are optional facilitation examples, not additional mandatory roles or events. Adapt them consistently with the [LeSS framework](https://less.works/less/framework).
## Overview
This template provides structured formats for conducting retrospectives in Large-Scale Scrum (LeSS) environments. LeSS retrospectives focus on both team-level and organizational improvements, emphasizing systemic thinking and cross-team collaboration.
## Template Information
- **Framework:** LeSS (Large-Scale Scrum)
- **Event Type:** Sprint Retrospective and Overall Retrospective
- **Duration:** 1.5-3 hours (depending on scope and number of teams)
- **Participants:** Teams, Scrum Masters, Product Owner(s), Management
- **Frequency:** Every sprint + quarterly overall retrospectives
---
## LeSS Retrospective Structure
### Two-Level Retrospective Approach
#### Team Retrospectives
**Duration:** 1.5 hours
**Participants:** Individual teams with their Scrum Masters
**Focus:** Team-specific improvements and local issues
#### Overall Retrospective
**Duration:** 2-3 hours
**Participants:** Representatives from all teams, Product Owner(s), Management
**Focus:** Cross-team coordination, organizational impediments, and systemic improvements
---
## Team Retrospective Format
### Standard Team Retrospective Agenda (1.5 hours)
#### Set the Stage (15 minutes)
**Objective:** Create a safe environment for open discussion
1. **Welcome and Check-in** (5 minutes)
- Brief personal check-in from each team member
- Set expectations for psychological safety
2. **Retrospective Prime Directive** (5 minutes)
- Read aloud: "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."
3. **Sprint Overview** (5 minutes)
- Quick review of sprint goals and achievements
- Context setting for the retrospective
#### Gather Data (30 minutes)
**Objective:** Collect information about what happened during the sprint
**Technique 1: Timeline Retrospective**
1. **Create Timeline** (15 minutes)
- Draw sprint timeline on board
- Team adds significant events, decisions, and feelings
- Use different colors for different types of events
2. **Discuss Patterns** (15 minutes)
- Identify patterns and trends
- Note emotional highs and lows
- Discuss cause and effect relationships
**Technique 2: Mad, Sad, Glad**
1. **Individual Reflection** (10 minutes)
- Each person writes items in three categories:
- Mad: Frustrations and anger
- Sad: Disappointments and missed opportunities
- Glad: Successes and positive experiences
2. **Share and Cluster** (20 minutes)
- Team shares items and groups similar themes
- Discuss most significant items in each category
#### Generate Insights (25 minutes)
**Objective:** Understand why things happened and identify improvements
1. **Root Cause Analysis** (15 minutes)
- For key issues identified, ask "5 Whys"
- Focus on systemic causes rather than blame
- Look for patterns across different issues
2. **Identify Systemic Issues** (10 minutes)
- Distinguish between team-controllable and organizational issues
- Note issues that affect multiple teams or external factors
- These will be escalated to Overall Retrospective
#### Decide What to Do (15 minutes)
**Objective:** Commit to specific improvement actions
1. **Brainstorm Solutions** (8 minutes)
- Generate ideas for addressing key issues
- Focus on actions within team's control
- Consider both quick wins and longer-term improvements
2. **Select Improvement Actions** (7 minutes)
- Choose 1-3 specific actions for next sprint
- Ensure actions are concrete and measurable
- Assign owners and timelines
#### Close the Retrospective (5 minutes)
1. **Summarize Actions** (3 minutes)
- Review selected improvement actions
- Confirm commitment from team
2. **Retrospective Feedback** (2 minutes)
- Quick feedback on retrospective process
- Note any improvements for next retrospective
---
## Overall Retrospective Format
### Quarterly Overall Retrospective Agenda (3 hours)
#### Opening and Context (30 minutes)
**Welcome and Introductions** (10 minutes)
- Welcome all participants
- Brief introductions if new people present
- Review retrospective objectives and process
**LeSS Retrospective Principles** (10 minutes)
- Focus on systemic improvement
- Address organizational impediments
- Encourage systems thinking
- Emphasize manager and management team participation
**Sprint/Quarter Overview** (10 minutes)
- Review key metrics and achievements
- Highlight cross-team collaborations
- Set context for improvement discussions
#### Data Gathering: Cross-Team Patterns (45 minutes)
**Team Reports** (30 minutes)
- Each team presents key insights from their retrospectives
- Focus on issues affecting multiple teams
- Identify patterns and systemic problems
**Organizational Impediments Review** (15 minutes)
- Review impediments that couldn't be resolved at team level
- Categorize by organizational area (HR, IT, Process, etc.)
- Prioritize by impact and urgency
#### System Analysis (60 minutes)
**Root Cause Analysis of Systemic Issues** (30 minutes)
- Select top 3-5 systemic issues
- Use fishbone diagrams or 5 Whys technique
- Include management perspective on organizational constraints
**Value Stream Mapping** (30 minutes)
- Map the flow of value from idea to customer
- Identify bottlenecks and waste in the system
- Highlight areas where teams are blocked by organizational factors
#### Break (15 minutes)
#### Solution Generation (45 minutes)
**Improvement Ideation** (25 minutes)
- Brainstorm solutions for systemic issues
- Include both process and structural improvements
- Consider what management and organization can change
**Impact vs. Effort Analysis** (20 minutes)
- Plot improvements on impact vs. effort matrix
- Focus on high-impact, low-effort wins
- Identify longer-term structural changes needed
#### Action Planning (40 minutes)
**Select Organizational Improvements** (20 minutes)
- Choose 3-5 improvements to implement
- Ensure management commitment for organizational changes
- Balance quick wins with strategic improvements
**Create Implementation Plans** (20 minutes)
- Define specific actions, owners, and timelines
- Identify success metrics and review points
- Plan communication to all teams
#### Closing (15 minutes)
**Commitment and Next Steps** (10 minutes)
- Confirm management and team commitment
- Schedule follow-up reviews
- Plan communication of decisions
**Retrospective Feedback** (5 minutes)
- Gather feedback on overall retrospective process
- Note improvements for next quarterly retrospective
---
## LeSS Retrospective Techniques
### Cross-Team Collaboration Analysis
#### Technique: Collaboration Heat Map
1. **Create Team Matrix** (15 minutes)
- List all teams on both axes of matrix
- Teams rate collaboration quality with each other team (1-5)
- Identify strongest and weakest collaboration points
2. **Discuss Patterns** (15 minutes)
- Why do some teams collaborate well?
- What barriers exist for poor collaboration?
- How can organization support better collaboration?
### Organizational Impediment Mapping
#### Technique: Impediment Ecosystem Map
1. **Map Impediment Sources** (20 minutes)
- Identify sources: HR policies, IT systems, management decisions, etc.
- Map relationships between different impediment sources
- Show impact on team effectiveness
2. **Prioritize by System Impact** (10 minutes)
- Focus on impediments affecting multiple teams
- Consider organizational change required
- Balance effort vs. benefit for removal
### Systems Thinking Exercises
#### Technique: Perspective Taking
1. **Multiple Viewpoints** (25 minutes)
- Teams discuss issues from different perspectives:
- Customer perspective
- Management perspective
- Other team perspective
- Organizational perspective
2. **Systemic Solutions** (15 minutes)
- Generate solutions that address root causes
- Consider unintended consequences
- Focus on win-win solutions for all stakeholders
---
## Retrospective Artifacts
### Team Retrospective Output Template
#### Team [Name] Sprint [Number] Retrospective
**Sprint Summary:**
- Sprint Goal: [Goal]
- Key Achievements: [List]
- Major Challenges: [List]
**What Went Well:**
1. [Success 1] - Why it worked
2. [Success 2] - Why it worked
3. [Success 3] - Why it worked
**What Didn't Go Well:**
1. [Challenge 1] - Root causes
2. [Challenge 2] - Root causes
3. [Challenge 3] - Root causes
**Improvement Actions for Next Sprint:**
| Action | Owner | Timeline | Success Criteria |
|--------|-------|----------|------------------|
| [Action 1] | [Name] | [Date] | [Criteria] |
| [Action 2] | [Name] | [Date] | [Criteria] |
**Organizational Impediments to Escalate:**
1. [Impediment 1] - Impact on team
2. [Impediment 2] - Impact on team
### Overall Retrospective Output Template
#### Overall Retrospective - [Quarter/Date]
**Systemic Issues Identified:**
1. [Issue 1] - Teams affected: [List]
2. [Issue 2] - Teams affected: [List]
3. [Issue 3] - Teams affected: [List]
**Organizational Improvements:**
| Improvement | Owner | Timeline | Success Metrics | Impact |
|------------|-------|----------|-----------------|---------|
| [Improvement 1] | [Role] | [Date] | [Metrics] | [Expected Impact] |
| [Improvement 2] | [Role] | [Date] | [Metrics] | [Expected Impact] |
**Management Commitments:**
- [Commitment 1] - [Manager name]
- [Commitment 2] - [Manager name]
**Follow-up Actions:**
- Next review: [Date]
- Communication plan: [How results will be shared]
- Progress tracking: [How progress will be monitored]
---
## Facilitation Guidelines
### Facilitation Principles for LeSS Retrospectives
#### Create Psychological Safety
- Emphasize learning over blame
- Model vulnerability as facilitator
- Encourage diverse perspectives
- Protect minority opinions
#### Focus on Systems
- Ask "why" questions to get to root causes
- Look for patterns across teams
- Consider organizational context
- Balance team autonomy with coordination needs
#### Engage Management
- Include managers in overall retrospectives
- Help managers understand their role in improvement
- Create safe space for management feedback
- Focus on systemic change management can influence
### Common Facilitation Challenges
#### Challenge: Teams Blame Other Teams
**Solution:**
- Redirect to systemic causes
- Use "How might we..." questions
- Focus on improving collaboration
- Look for organizational root causes
#### Challenge: Management Doesn't Attend
**Solution:**
- Start with willing managers
- Show value through small improvements
- Create safe environment for management participation
- Demonstrate business impact of improvements
#### Challenge: Too Many Issues to Address
**Solution:**
- Use prioritization techniques (dot voting, impact/effort matrix)
- Focus on systemic issues affecting multiple teams
- Start with quick wins to build momentum
- Create parking lot for future consideration
---
## Tools and Techniques
### Digital Retrospective Tools
#### Recommended Tools
**FunRetro/RetroTool:**
- Online retrospective boards
- Real-time collaboration
- Template library
- Action item tracking
**Miro/Mural:**
- Visual collaboration space
- Custom retrospective templates
- Integration with other planning tools
- Excellent for system mapping exercises
**Microsoft Teams/Zoom + Whiteboard:**
- Built-in collaboration tools
- Screen sharing for facilitation
- Breakout rooms for small group work
- Recording capability for later review
### Physical Retrospective Setup
#### Room Setup for Overall Retrospective
```
Overall Retrospective Room Layout
Facilitator Area Timeline Wall
┌─────────────┐ ┌─────────────────────┐
│ Flipcharts │ │ Sprint/Quarter │
│ Markers │ │ Timeline │
│ Stickies │ │ │
└─────────────┘ └─────────────────────┘
Team A Table Team B Table
┌─────────────┐ Action ┌─────────────┐
│ 4-5 people │ Board │ 4-5 people │
│ │ │ │
└─────────────┘ └─────────────┘
Team C Table Team D Table
┌─────────────┐ ┌─────────────┐
│ 4-5 people │ │ 4-5 people │
│ │ │ │
└─────────────┘ └─────────────┘
Management Table
┌─────────────────────┐
│ Managers/Leaders │
│ │
└─────────────────────┘
```
#### Materials Needed
- Large wall space for timeline and system maps
- Sticky notes (multiple colors)
- Markers and pens
- Flip chart paper
- Dot stickers for voting
- Timer for timeboxing
- Camera for capturing outputs
---
## Success Metrics
### Retrospective Effectiveness Metrics
- **Participation Rate:** Percentage of team members attending
- **Action Completion:** Percentage of improvement actions completed
- **Satisfaction Score:** Team rating of retrospective value (1-5)
- **Systemic Focus:** Percentage of improvements addressing organizational issues
### Organizational Improvement Metrics
- **Cross-Team Issues:** Reduction in cross-team impediments over time
- **Cycle Time:** Improvement in overall value delivery speed
- **Team Health:** Improvement in team satisfaction scores
- **Collaboration Quality:** Improvement in cross-team collaboration ratings
### Management Engagement Metrics
- **Management Attendance:** Consistency of management participation
- **Commitment Follow-through:** Percentage of management commitments delivered
- **Organizational Changes:** Number of structural/policy changes made
- **Investment in Improvements:** Budget/time allocated to retrospective actions
---
## Continuous Improvement of Retrospectives
### Meta-Retrospective Questions
1. **Process Effectiveness:**
- Are our retrospectives leading to meaningful improvements?
- Do we focus enough on systemic issues?
- Is management engagement sufficient?
2. **Facilitation Quality:**
- Do all voices get heard in retrospectives?
- Are we creating psychological safety?
- Are our techniques engaging and effective?
3. **Follow-through:**
- Do we complete the actions we commit to?
- Are we tracking the impact of our improvements?
- How can we better sustain changes?
### Retrospective Evolution
- **Quarterly Process Review:** Assess and adjust retrospective format
- **Facilitator Development:** Improve facilitation skills across Scrum Masters
- **Technique Variety:** Experiment with new retrospective techniques
- **Management Coaching:** Help managers become better retrospective participants
---
## Related Templates
- [LeSS Sprint Planning Template](../../../../../delivery/methodology-frameworks/agile-scrum/scaling-frameworks/less/less_sprint_planning_template.md)
- [Overall Product Backlog Management](../../../../../delivery/methodology-frameworks/agile-scrum/scaling-frameworks/less/overall_product_backlog_template.md)
- [Cross-Team Coordination Template](../../../../../delivery/methodology-frameworks/agile-scrum/scaling-frameworks/less/cross_team_coordination_template.md)
- [LeSS Adoption Roadmap](../../../../../../quick-start-kits/less-adoption/README.md)
---
## Version History
| Version | Date | Changes | Author |
|---------|------|---------|--------|
| 1.0 | [Date] | Initial LeSS Retrospective template | [Author] |
---
*This template is part of the PM Tools Templates library. For more information and additional templates, visit [repository root](../../../../README.md).*