agile-retrospective

When facilitating sprint retrospectives or team improvement sessions.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026

When & Why to Use This Skill

This Claude skill streamlines the Agile retrospective process by providing structured frameworks like 'Start/Stop/Continue' and '4Ls'. It is designed to help Scrum Masters and project leads facilitate high-impact team improvement sessions, ensuring that discussions lead to measurable action items rather than just general feedback. By incorporating facilitation tips and identifying common anti-patterns, it enhances team velocity and fosters a culture of continuous improvement.

Use Cases

  • Sprint Retrospectives: Facilitating a structured end-of-sprint meeting to evaluate what went well and what needs to change for the next cycle.
  • Team Health Checks: Running periodic improvement sessions to address team friction, communication bottlenecks, and workflow inefficiencies.
  • Action Item Generation: Transforming vague feedback into SMART (Specific, Measurable, Achievable, Relevant, Time-bound) action items with assigned owners and deadlines.
  • Process Standardization: Implementing consistent retrospective formats across multiple engineering or business teams to ensure quality and accountability.
nameagile-retrospective
descriptionWhen facilitating sprint retrospectives or team improvement sessions.
version1.0.0
tokens~300
confidencehigh
- https//www.scrum.org/resources/what-is-a-sprint-retrospective
last_validated2025-01-10
next_review2025-01-24
tags[agile, retrospective, scrum, planning]

When to Use

When facilitating sprint retrospectives or team improvement sessions.

Patterns

Start/Stop/Continue Format

## Sprint X Retrospective

### 🟢 START (new practices)
- [What should we begin doing?]
- [New tools, processes, habits]

### 🔴 STOP (remove friction)
- [What should we stop doing?]
- [What's not working?]

### 🟡 CONTINUE (keep doing)
- [What's working well?]
- [What should we keep?]

### 📋 Action Items
| Action | Owner | Due |
|--------|-------|-----|
| [specific action] | [name] | [date] |

4Ls Format (Alternative)

LIKED:    What went well?
LEARNED:  What did we learn?
LACKED:   What was missing?
LONGED:   What do we wish for?

Facilitation Tips

1. Timebox: 45-60 min max
2. Equal voice: everyone speaks
3. No blame: focus on process, not people
4. Action items: max 3, specific, owned
5. Follow-up: review last retro's actions first

Action Item Quality

❌ "Improve communication"
✅ "Daily 10min sync at 9am, owner: @lead, starts Monday"

❌ "Write more tests"
✅ "Add integration tests for auth module, owner: @dev, by Sprint end"

Anti-Patterns

  • No action items (talk shop only)
  • Too many action items (>3 = none done)
  • Blame individuals instead of process
  • Skip reviewing last sprint's actions
  • Manager dominates discussion

Verification Checklist

  • All team members contributed
  • Max 3 action items
  • Each action has owner + date
  • Previous actions reviewed
  • Notes documented