Data-Driven Retrospectives | Metrics + Insights
Use data to drive retrospective discussions with velocity, cycle time, and defect metrics. GitScrum balances numbers with team insights for better outcomes.
9 min read
Data illuminates patterns. GitScrum provides metrics that help teams have data-informed retrospectives, balancing numbers with human insight.
Data in Retrospectives
Why Use Data
DATA-INFORMED RETROSPECTIVES:
┌─────────────────────────────────────────────────────────────┐
│ │
│ WITHOUT DATA: │
│ ───────────── │
│ "I feel like we had a lot of bugs this sprint" │
│ "It seems like reviews took forever" │
│ "I think scope kept changing" │
│ │
│ PROBLEMS: │
│ • Based on recent memory (recency bias) │
│ • Loud voices dominate │
│ • Hard to spot trends │
│ • Subjective without evidence │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ WITH DATA: │
│ ────────── │
│ "We had 3 production bugs, same as last 3 sprints" │
│ "Review time averaged 2.4 days, up from 1.8 days" │
│ "4 stories were added mid-sprint, 2 were removed" │
│ │
│ BENEFITS: │
│ • Objective starting point │
│ • Trends visible │
│ • Everyone working from same facts │
│ • Progress measurable │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ KEY PRINCIPLE: │
│ ────────────── │
│ Data INFORMS discussion, doesn't replace it │
│ Numbers + Human insight = Full picture │
│ │
│ "The data shows X happened. Why do we think that is?" │
└─────────────────────────────────────────────────────────────┘
Metrics to Review
Sprint Metrics
RETROSPECTIVE DATA PACKAGE:
┌─────────────────────────────────────────────────────────────┐
│ │
│ DELIVERY METRICS: │
│ ───────────────── │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ SPRINT 15 SUMMARY ││
│ │ ││
│ │ VELOCITY: ││
│ │ Committed: 40 pts Completed: 35 pts (88%) ││
│ │ Trend: ████████████████████████████░░ 88% ││
│ │ Last 4 sprints: 32, 38, 35, 35 ││
│ │ ││
│ │ STORIES: ││
│ │ Planned: 8 Completed: 7 Carried over: 1 ││
│ │ ││
│ │ SCOPE CHANGES: ││
│ │ Added: 2 stories (8 pts) ││
│ │ Removed: 1 story (5 pts) ││
│ │ Net: +3 pts mid-sprint ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ FLOW METRICS: │
│ ───────────── │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ CYCLE TIME: ││
│ │ Average: 4.2 days (target: <5) ✅ ││
│ │ Trend: 3.8 → 4.0 → 4.2 → 4.2 (stable) ││
│ │ ││
│ │ BREAKDOWN: ││
│ │ In Dev: 2.1 days ██████████████████████ ││
│ │ In Review: 1.5 days ███████████████ ││
│ │ In QA: 0.6 days ██████ ││
│ │ ││
│ │ Review time up from 1.1 days last sprint ⚠️ ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ QUALITY METRICS: │
│ ─────────────── │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ DEFECTS: ││
│ │ Escaped to prod: 2 (target: <3) ✅ ││
│ │ Found in testing: 8 ││
│ │ Defect ratio: 20% (2 escaped / 10 total) ││
│ │ ││
│ │ TEST COVERAGE: ││
│ │ New code: 82% (target: >80%) ✅ ││
│ │ Overall: 71% ││
│ └─────────────────────────────────────────────────────────┘│
└─────────────────────────────────────────────────────────────┘
Team Health
TEAM HEALTH DATA:
┌─────────────────────────────────────────────────────────────┐
│ │
│ TEAM CONFIDENCE: │
│ ──────────────── │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ "How confident were you we'd meet sprint goal?" ││
│ │ ││
│ │ Sprint 12: ████████████████████████████████ 4.5 ││
│ │ Sprint 13: ██████████████████████████████ 4.2 ││
│ │ Sprint 14: ██████████████████████████ 3.8 ││
│ │ Sprint 15: ████████████████████████ 3.5 ⚠️ ││
│ │ ││
│ │ Declining trend worth discussing ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ BLOCKERS: │
│ ────────── │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ Blocker count: 5 total ││
│ │ Average resolution: 1.8 days ││
│ │ ││
│ │ BY TYPE: ││
│ │ • Dependencies (external team): 2 ││
│ │ • Unclear requirements: 2 ││
│ │ • Technical issues: 1 ││
│ │ ││
│ │ Pattern: External dependencies causing delays ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ INTERRUPTIONS: │
│ ────────────── │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ Unplanned work: 15% of capacity ││
│ │ ││
│ │ Breakdown: ││
│ │ • Production support: 8% ││
│ │ • Urgent bugs: 5% ││
│ │ • Meetings: 2% ││
│ │ ││
│ │ Trend: 10% → 12% → 15% (increasing) ⚠️ ││
│ └─────────────────────────────────────────────────────────┘│
└─────────────────────────────────────────────────────────────┘
Retro Format
Data-Driven Structure
RETROSPECTIVE FORMAT:
┌─────────────────────────────────────────────────────────────┐
│ │
│ DATA-DRIVEN RETRO AGENDA: │
│ ───────────────────────── │
│ │
│ 1. REVIEW DATA (10 min) │
│ Share sprint metrics │
│ Highlight trends and anomalies │
│ No interpretation yet, just facts │
│ │
│ 2. INITIAL REACTIONS (5 min) │
│ "What stands out?" │
│ "What surprises you?" │
│ "What matches your experience?" │
│ │
│ 3. DEEP DIVE (20 min) │
│ Pick 1-2 data points to explore │
│ "Why do we think this happened?" │
│ "What's the root cause?" │
│ │
│ 4. QUALITATIVE CHECK (10 min) │
│ "What doesn't show in the data?" │
│ Team health, morale, challenges │
│ What the numbers miss │
│ │
│ 5. ACTION ITEMS (10 min) │
│ Specific, measurable improvements │
│ How will we know if it worked? │
│ Owner and timeline │
│ │
│ 6. CHECK PREVIOUS ACTIONS (5 min) │
│ Did previous improvements work? │
│ Data shows impact? │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ FACILITATION QUESTIONS: │
│ ─────────────────────── │
│ • "The data shows X. What's behind that number?" │
│ • "We expected Y but got Z. What happened?" │
│ • "This metric improved. What did we do differently?" │
│ • "Does this match how you felt during the sprint?" │
└─────────────────────────────────────────────────────────────┘
Avoiding Pitfalls
Healthy Data Culture
DATA PITFALLS TO AVOID:
┌─────────────────────────────────────────────────────────────┐
│ │
│ PITFALL: BLAME │
│ ────────────── │
│ ❌ "Alex only completed 3 stories" │
│ ✅ "3 of our stories took longer than expected. Why?" │
│ │
│ Focus on systems, not individuals │
│ What enabled the situation? │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ PITFALL: GAMING METRICS │
│ ─────────────────────── │
│ ❌ "We need to hit velocity target" │
│ → Team inflates story points │
│ → Metrics become meaningless │
│ │
│ ✅ Use metrics to understand, not judge │
│ No targets tied to individual performance │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ PITFALL: IGNORING QUALITATIVE │
│ ───────────────────────────── │
│ ❌ "The data looks fine, nothing to discuss" │
│ │
│ ✅ "Numbers look good. How did it FEEL?" │
│ Team might be burning out but still delivering │
│ Data doesn't capture everything │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ PITFALL: OVER-ANALYSIS │
│ ────────────────────── │
│ ❌ 30 minutes reviewing 20 metrics │
│ │
│ ✅ 5-10 minutes on 3-5 key metrics │
│ Leave time for discussion │
│ Focus on what matters most │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ THE BALANCE: │
│ ──────────── │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ ││
│ │ DATA provides objectivity and trends ││
│ │ DISCUSSION provides context and insight ││
│ │ TOGETHER = Better decisions ││
│ │ ││
│ │ Data without discussion = Cold and incomplete ││
│ │ Discussion without data = Biased and unfocused ││
│ │ ││
│ └─────────────────────────────────────────────────────────┘│
└─────────────────────────────────────────────────────────────┘
Tracking Improvement
Measuring Actions
TRACKING RETRO OUTCOMES:
┌─────────────────────────────────────────────────────────────┐
│ │
│ ACTION ITEM TRACKING: │
│ ───────────────────── │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ SPRINT 15 RETRO ACTIONS ││
│ │ ││
│ │ ACTION OWNER MEASURE STATUS ││
│ │ ────── ───── ─────── ────── ││
│ │ Reduce review @all Review time Complete ✅ ││
│ │ time to <1 day < 1 day Now at 0.8 days ││
│ │ ││
│ │ Daily dependency @jordan Dependencies In Progress ││
│ │ check-in resolved 2/5 addressed ││
│ │ faster ││
│ │ ││
│ │ Document API @alex Support Not Started ││
│ │ better tickets ↓ ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ IMPROVEMENT TRENDS: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ METRICS OVER TIME ││
│ │ ││
│ │ PROBLEM: Long review times ││
│ │ ACTION: Review SLA, pairing on reviews (Sprint 13) ││
│ │ ││
│ │ Sprint 12: 2.4 days ████████████████████████ ││
│ │ Sprint 13: 1.8 days ██████████████████ (action) ││
│ │ Sprint 14: 1.1 days ███████████ ││
│ │ Sprint 15: 0.8 days ████████ ✅ ││
│ │ ││
│ │ Improvement sustained! Can mark complete. ││
│ │ ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ REVIEW PAST ACTIONS: │
│ ──────────────────── │
│ Every retro: │
│ • Did we do what we said? │
│ • Did it have the expected impact? │
│ • Continue, adjust, or abandon? │
│ │
│ CELEBRATE IMPROVEMENTS: │
│ ──────────────────────── │
│ When data shows improvement, acknowledge it! │
│ Reinforces that retros lead to real change │
└─────────────────────────────────────────────────────────────┘