Sprint Health Indicators | Early Warning Metrics
Monitor sprint health with burndown charts, blocker counts, and team confidence. GitScrum provides leading indicators to detect problems early.
9 min read
Healthy sprints deliver value. GitScrum provides sprint health indicators that help teams spot problems early and take corrective action.
Sprint Health Overview
Key Indicators
SPRINT HEALTH INDICATORS:
┌─────────────────────────────────────────────────────────────┐
│ │
│ HEALTH DASHBOARD: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ SPRINT 15 HEALTH Day 6 of 10 ││
│ │ ││
│ │ OVERALL: 🟢 HEALTHY ││
│ │ ││
│ │ ┌─────────────────────────────────────────────────────┐││
│ │ │ INDICATOR STATUS DETAIL │││
│ │ │ ───────── ────── ────── │││
│ │ │ Burndown 🟢 On track (60% done) │││
│ │ │ Blockers 🟢 0 active blockers │││
│ │ │ Scope 🟢 No changes │││
│ │ │ Team Confidence 🟢 4.2/5 average │││
│ │ │ Work in Review 🟡 3 items (2 days avg) │││
│ │ │ Velocity Trend 🟢 +5% vs average │││
│ │ └─────────────────────────────────────────────────────┘││
│ │ ││
│ │ 🟢 = Healthy 🟡 = Watch 🔴 = Action needed ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ INDICATOR TYPES: │
│ ──────────────── │
│ │
│ LEADING (Predict problems): │
│ • Blockers count │
│ • Work stuck in progress │
│ • Team confidence │
│ │
│ LAGGING (Show results): │
│ • Stories completed │
│ • Sprint goal progress │
│ • Velocity │
│ │
│ Both are needed for complete picture │
└─────────────────────────────────────────────────────────────┘
Burndown Analysis
Reading Burndown Charts
BURNDOWN PATTERNS:
┌─────────────────────────────────────────────────────────────┐
│ │
│ HEALTHY BURNDOWN: │
│ ───────────────── │
│ Points │
│ 40 │● │
│ │ ● │
│ 30 │ ● │
│ │ ● │
│ 20 │ ● ← Following ideal line │
│ │ ● │
│ 10 │ ● │
│ │ ● │
│ 0 │───────────────●─────────────────→ Days │
│ 1 2 3 4 5 6 7 8 9 10 │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ FLAT BURNDOWN (⚠️ Warning): │
│ ─────────────────────────── │
│ Points │
│ 40 │●──●──●──●──● │
│ │ ← Work started but nothing finishing │
│ 30 │ │
│ │ │
│ 20 │ Ideal line │
│ │ ↘ │
│ 10 │ │
│ │ │
│ 0 │─────────────────────────────────→ Days │
│ │
│ CAUSES: │
│ • Work too big (not broken down) │
│ • Blockers preventing completion │
│ • Too much WIP │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ LATE SURGE (⚠️ Risk): │
│ ────────────────── │
│ Points │
│ 40 │●──●──●──●──●──● │
│ │ ● │
│ 30 │ ● │
│ │ ● │
│ 20 │ ● │
│ │ ● │
│ 10 │ ● │
│ │ ● │
│ 0 │───────────────────────────────●→ │
│ │
│ Most work done in final days = Risk of incomplete/rushed │
└─────────────────────────────────────────────────────────────┘
Blocker Tracking
Managing Blockers
BLOCKER INDICATORS:
┌─────────────────────────────────────────────────────────────┐
│ │
│ BLOCKER DASHBOARD: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ CURRENT BLOCKERS ││
│ │ ││
│ │ 🔴 Active: 1 🟡 At risk: 2 ✅ Resolved: 4 ││
│ │ ││
│ │ ┌─────────────────────────────────────────────────────┐││
│ │ │ 🔴 STORY-234: API spec not finalized │││
│ │ │ Blocked: 3 days │││
│ │ │ Owner: @alex │││
│ │ │ Impact: 3 dependent stories │││
│ │ │ Action: Meeting scheduled today 2pm │││
│ │ └─────────────────────────────────────────────────────┘││
│ │ ││
│ │ ┌─────────────────────────────────────────────────────┐││
│ │ │ 🟡 STORY-245: Waiting for design review │││
│ │ │ Waiting: 1 day │││
│ │ │ At risk of becoming blocker │││
│ │ └─────────────────────────────────────────────────────┘││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ BLOCKER HEALTH: │
│ ─────────────── │
│ │
│ 🟢 HEALTHY: │
│ • 0 blockers OR │
│ • All blockers < 1 day old with clear resolution │
│ │
│ 🟡 WATCH: │
│ • 1-2 blockers │
│ • Blockers 1-2 days old │
│ • Resolution in progress │
│ │
│ 🔴 ACTION NEEDED: │
│ • 3+ blockers │
│ • Any blocker > 2 days │
│ • No clear resolution path │
│ • Blockers affecting sprint goal │
│ │
│ DAILY STANDUP: │
│ ───────────── │
│ "What's blocked?" is THE most important question │
│ Unblock before starting new work │
└─────────────────────────────────────────────────────────────┘
Scope Health
Tracking Scope Changes
SCOPE CHANGE TRACKING:
┌─────────────────────────────────────────────────────────────┐
│ │
│ SPRINT SCOPE: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ SPRINT 15 SCOPE ││
│ │ ││
│ │ ORIGINAL: 42 points (8 stories) ││
│ │ CURRENT: 48 points (10 stories) ││
│ │ CHANGE: +6 points (+14%) ⚠️ ││
│ │ ││
│ │ ADDITIONS: ││
│ │ + STORY-278 (3 pts) - Urgent bug ││
│ │ + STORY-289 (5 pts) - Exec request ││
│ │ ││
│ │ REMOVALS: ││
│ │ - STORY-256 (2 pts) - Deprioritized ││
│ │ ││
│ │ NET: +6 points ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ SCOPE HEALTH: │
│ ───────────── │
│ │
│ 🟢 HEALTHY: │
│ • No scope changes OR │
│ • Changes < 10% AND balanced (adds = removes) │
│ │
│ 🟡 WATCH: │
│ • 10-20% scope increase │
│ • Multiple mid-sprint additions │
│ │
│ 🔴 ACTION NEEDED: │
│ • > 20% scope increase │
│ • Additions without removals │
│ • Sprint goal at risk │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ SCOPE CHANGE RULES: │
│ ─────────────────── │
│ • Adding? Remove something equivalent │
│ • PO makes final call on priority │
│ • Team makes final call on capacity │
│ • Track ALL changes for transparency │
└─────────────────────────────────────────────────────────────┘
Team Confidence
Measuring Confidence
TEAM CONFIDENCE INDICATOR:
┌─────────────────────────────────────────────────────────────┐
│ │
│ CONFIDENCE CHECK: │
│ ───────────────── │
│ │
│ Quick poll in standup (weekly or mid-sprint): │
│ "How confident are you we'll complete the sprint goal?" │
│ │
│ SCALE: 1-5 │
│ 1 = Not at all │
│ 5 = Completely confident │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ TEAM CONFIDENCE TREND: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ ││
│ │ SPRINT 15 CONFIDENCE ││
│ │ ││
│ │ Day 1: ████████████████████████████████ 4.5 ││
│ │ Day 3: ██████████████████████████████ 4.2 ││
│ │ Day 6: ████████████████████████ 3.8 ⚠️ ││
│ │ ││
│ │ BY MEMBER: ││
│ │ @alex: ████████████████████ 4.0 ││
│ │ @jordan: ██████████████████████ 4.5 ││
│ │ @pat: ████████████████ 3.0 ← Discuss privately ││
│ │ @sam: ██████████████████████████ 5.0 ││
│ │ ││
│ │ Dropping confidence needs discussion ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ INTERPRETING CONFIDENCE: │
│ ──────────────────────── │
│ │
│ 🟢 Average ≥ 4.0: Sprint on track │
│ 🟡 Average 3.0-3.9: Risks to address │
│ 🔴 Average < 3.0: Sprint in trouble │
│ │
│ LOW CONFIDENCE → ASK WHY: │
│ • Hidden blockers? │
│ • Underestimated complexity? │
│ • External dependencies? │
│ • Personal issues? │
│ │
│ RULE: Don't punish low confidence │
│ It's an early warning system, not a judgment │
└─────────────────────────────────────────────────────────────┘
Taking Action
When Health is Poor
RESPONDING TO POOR HEALTH:
┌─────────────────────────────────────────────────────────────┐
│ │
│ RED INDICATORS → IMMEDIATE ACTION: │
│ ────────────────────────────────── │
│ │
│ 1. IDENTIFY ROOT CAUSE │
│ Quick sync with team │
│ What's causing the problem? │
│ │
│ 2. ADDRESS BLOCKERS │
│ Swarm on blocked items │
│ Escalate if needed │
│ Make it team's #1 priority │
│ │
│ 3. REDUCE SCOPE │
│ If capacity exceeded: │
│ • Remove lowest priority items │
│ • Negotiate with PO │
│ • Protect sprint goal │
│ │
│ 4. COMMUNICATE │
│ Stakeholders need to know risks │
│ Early warning is better than surprise │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ SPRINT RECOVERY OPTIONS: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ ││
│ │ OPTION 1: REDUCE SCOPE ││
│ │ Remove stories, protect sprint goal ││
│ │ Best when: Overcommitted, can defer work ││
│ │ ││
│ │ OPTION 2: SWARM ││
│ │ Everyone focuses on unblocking ││
│ │ Best when: Specific bottleneck ││
│ │ ││
│ │ OPTION 3: GET HELP ││
│ │ Borrow capacity, get expertise ││
│ │ Best when: Skill gap or capacity gap ││
│ │ ││
│ │ OPTION 4: ACCEPT PARTIAL DELIVERY ││
│ │ Acknowledge sprint goal won't be met ││
│ │ Best when: Already too late, learn from it ││
│ │ ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ IN RETROSPECTIVE: │
│ ───────────────── │
│ Discuss what indicators showed │
│ Did we act on them early enough? │
│ How to prevent next time? │
└─────────────────────────────────────────────────────────────┘