Facilitate effective retrospectives to capture lessons learned, celebrate successes, and identify actionable improvements for future iterations.

Retrospective Facilitation Table of Contents [Overview]( overview) [When to Use]( when to use) [Quick Start]( quick start) [Reference Guides]( reference guides) [Best Practices]( best practices) Overview Retrospectives are critical ceremonies for team learning and continuous improvement. Effective facilitation creates psychological safety, encourages honest feedback, and drives tangible improvements. When to Use End of sprint (regular cadence) Major milestone completion Project closure After significant events or incidents Team transitions or staff changes Technology implementations Process evaluations Quick Start Minimal working example: Reference Guides Detailed implementations in the references/ directory: Guide Contents [Retrospective Planning](references/retrospective planning.md) Retrospective Planning [Facilitation Techniques](references/facilitation techniques.md) Facilitation Techniques [Action Item Tracking](references/action item tracking.md) Action Item Tracking [Retrospective Templates](references/retrospective templates.md) Retrospective Templates Best Practices ✅ DO Hold retrospectives regularly (every sprint) Create psychological safety upfront Use varied formats to maintain engagement Include the whole team Focus on systems, not individuals Convert insights to specific action items Assign clear owners and due dates Track and celebrate completed actions Review previous actions at start Thank people for participation and honesty ❌ DON'T Blame individuals or teams Let dominant voices control discussion Create action items without owners Have retrospectives without follow up Ignore difficult feedback Focus only on what went wrong Hold retrospectives when people are tired/stressed Skip closing/celebration Mix retrospectives with status meetings Ignore patterns across multiple retrospectives

retrospective-facilitation