retrospective

# Sprint Retrospective Facilitator Run a DreamTeam sprint retrospective (30-60 min). ## Format: Start / Stop / Continue + Action Items ### Step 1: Set the Stage (5 min) - Welcome everyone, remind team this is a safe space - Establish working agreements: honest, constructive, no blame - Review previous retro action items — were they completed? ### Step 2: Gather Data (15 min) Ask each team member to contribute to three categories: **🟢 WHAT WENT WELL? (Continue doing)** - Technical wins - Team collaboration highlights - Process improvements that worked - Deliverables completed successfully **🔴 WHAT DIDN'T GO WELL? (Stop doing)** - Blockers that slowed us down - Process failures - Communication breakdowns - Quality issues that slipped through **🟡 WHAT SHOULD WE START DOING? (Start doing)** - New practices to try - Tools or processes to adopt - Communication improvements - Technical improvements ### Step 3: Group & Vote (10 min) - Group similar items together - Each team member gets 3 votes (dot voting) - Vote on what to address first - Top 3-5 items move to action planning ### Step 4: Action Items (15 min) For each top-voted item, create an action: ``` Issue: [what the problem is] Root cause: [why it happened — use 5 Whys if needed] Action: [specific, measurable change to make] Owner: [one person responsible] Due: [by next sprint? by EOW?] Success metric: [how do we know it worked?] ``` ### Step 5: Appreciations (5 min) Each person gives one shout-out to a teammate. Builds psychological safety. ### Step 6: Close (2 min) - Recap action items and owners - Schedule follow-up check-in for mid-sprint - Team rates the retro: 1-5 stars (quick pulse) ## Output Format ``` 🔄 SPRINT [N] RETROSPECTIVE Date: [date] | Attendees: [list roles] 📈 SPRINT METRICS: Velocity: [planned] pts → [completed] pts ([X]%) Stories completed: [N]/[N] Bugs found: [N] | Bugs fixed: [N] ✅ WHAT WENT WELL: ⭐ [Item] (votes: N) ⭐ [Item] (votes: N) 🔴 WHAT DIDN'T GO WELL: ⚠️ [Item] (votes: N) ⚠️ [Item] (votes: N) 💡 WHAT TO START DOING: → [Item] (votes: N) → [Item] (votes: N) 🎯 ACTION ITEMS: 1. [Action] — Owner: [Role] — Due: [date] 2. [Action] — Owner: [Role] — Due: [date] 3. [Action] — Owner: [Role] — Due: [date] 🙏 APPRECIATIONS: [Role] → [Role]: "[appreciation]" ⭐ RETRO RATING: [N]/5 ✅ RETROSPECTIVE COMPLETE — Next sprint starts: [date] ``` ## Rules - All voices equal — no hierarchy in retro - Focus on systems and processes, not individuals - Every action item must have one owner - Action items created as Kanboard tasks before retro ends - Previous retro actions reviewed at the start of every retro