Manage Blockers Effectively | Detection & Escalation
Identify and resolve blockers fast with escalation paths, triage dashboards, and pattern analysis. GitScrum tracks blocked time and recurring obstacles.
7 min read
Unresolved blockers are silent sprint killers. GitScrum helps teams flag, track, and escalate blockers quickly with visibility features that ensure no obstacle goes unaddressed for too long.
Blocker Types
Common Blockers
BLOCKER CATEGORIES:
┌─────────────────────────────────────────────────────────────┐
│ │
│ DEPENDENCY BLOCKERS: │
│ • Waiting for another team's work │
│ • External API not ready │
│ • Waiting for design assets │
│ • Blocked by upstream bug │
│ │
│ TECHNICAL BLOCKERS: │
│ • Infrastructure issue │
│ • Build/CI broken │
│ • Environment unavailable │
│ • Technical debt preventing progress │
│ │
│ INFORMATION BLOCKERS: │
│ • Requirements unclear │
│ • Missing specifications │
│ • Questions awaiting answers │
│ • Need stakeholder decision │
│ │
│ RESOURCE BLOCKERS: │
│ • Missing access/credentials │
│ • Waiting for license │
│ • Need hardware/equipment │
│ • Person unavailable │
│ │
│ APPROVAL BLOCKERS: │
│ • Waiting for sign-off │
│ • Legal/compliance review │
│ • Budget approval needed │
│ • Security review pending │
└─────────────────────────────────────────────────────────────┘
Blocker Impact
IMPACT ASSESSMENT:
┌─────────────────────────────────────────────────────────────┐
│ │
│ BLOCKER SEVERITY: │
│ │
│ 🔴 CRITICAL: │
│ • Team cannot work at all │
│ • Multiple tasks blocked │
│ • Sprint goal at risk │
│ Response: Immediate escalation │
│ │
│ 🟡 HIGH: │
│ • Individual blocked completely │
│ • 1-2 tasks blocked │
│ • Will impact sprint if unresolved │
│ Response: Same-day action required │
│ │
│ 🟢 MEDIUM: │
│ • Work slowed but continuing │
│ • Workaround exists │
│ • Can wait a day or two │
│ Response: Resolve within 48 hours │
│ │
│ COST CALCULATION: │
│ │
│ 1 blocked developer = $X/day lost productivity │
│ 3 days blocked × 2 devs = 6 days productivity lost │
│ │
│ Plus: Context switching, frustration, cascading delays │
│ │
│ URGENCY: Resolve blockers fast, cost grows daily │
└─────────────────────────────────────────────────────────────┘
Resolution Process
Surfacing Blockers
MAKING BLOCKERS VISIBLE:
┌─────────────────────────────────────────────────────────────┐
│ │
│ WHEN TO FLAG: │
│ • The moment you realize you're blocked │
│ • Don't wait for standup │
│ • Don't assume someone knows │
│ │
│ HOW TO FLAG: │
│ │
│ TASK LEVEL: │
│ • Mark task as blocked in GitScrum │
│ • Add blocker reason │
│ • Tag who can help │
│ │
│ COMMUNICATION: │
│ • Post in team channel │
│ • Mention in daily standup │
│ • DM the person who can help │
│ │
│ BLOCKER FORMAT: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ 🚧 BLOCKED: Task #234 - Payment integration ││
│ │ ││
│ │ **What:** Need Stripe API test credentials ││
│ │ **Why:** Can't proceed with integration testing ││
│ │ **Who can help:** @DevOps ││
│ │ **Impact:** Blocking 3 downstream tasks ││
│ │ **Blocked since:** Monday 2pm ││
│ │ **Need by:** Wednesday EOD to stay on track ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ GOOD BLOCKER DESCRIPTIONS GET FASTER RESOLUTION │
└─────────────────────────────────────────────────────────────┘
Escalation Path
BLOCKER ESCALATION:
┌─────────────────────────────────────────────────────────────┐
│ │
│ LEVEL 1: SELF-RESOLVE (0-2 hours) │
│ • Try to solve independently │
│ • Check documentation │
│ • Ask teammate │
│ │
│ LEVEL 2: TEAM CHANNEL (2-4 hours) │
│ • Post blocker in team channel │
│ • Tag specific people who might help │
│ • Provide full context │
│ │
│ LEVEL 3: DIRECT ESCALATION (4-8 hours) │
│ • DM specific person needed │
│ • Involve team lead │
│ • Cross-team request if dependency │
│ │
│ LEVEL 4: MANAGEMENT (>8 hours) │
│ • Escalate to manager │
│ • May need organizational intervention │
│ • Formal escalation path │
│ │
│ ESCALATION CRITERIA: │
│ • Time-based: No response within timeframe │
│ • Impact-based: Critical blockers escalate faster │
│ • Sprint-based: Escalate if sprint goal at risk │
│ │
│ ESCALATION IS NOT FAILURE │
│ It's getting the right help for the situation │
└─────────────────────────────────────────────────────────────┘
Tracking & Metrics
Blocker Dashboard
BLOCKER TRACKING:
┌─────────────────────────────────────────────────────────────┐
│ Active Blockers │
├─────────────────────────────────────────────────────────────┤
│ │
│ Task │ Blocker │ Owner │ Days │ Severity │
│─────────────┼─────────────┼─────────┼──────┼──────────────│
│ #234 │ API creds │ @devops │ 2 │ 🔴 Critical │
│ #256 │ Design spec │ @design │ 1 │ 🟡 High │
│ #289 │ Legal review│ @legal │ 3 │ 🟡 High │
│ │
│ SUMMARY: │
│ Active blockers: 3 │
│ Total blocked time: 6 dev-days this sprint │
│ Avg resolution time: 1.8 days │
│ │
│ TREND (last 5 sprints): │
│ S20: █████████ 9 blockers │
│ S21: ██████ 6 blockers │
│ S22: ████████ 8 blockers │
│ S23: █████ 5 blockers │
│ S24: ███ 3 blockers (current) │
│ │
│ INSIGHT: Blocker count decreasing, │
│ but API credential issues recurring │
└─────────────────────────────────────────────────────────────┘
Pattern Analysis
BLOCKER PATTERNS:
┌─────────────────────────────────────────────────────────────┐
│ │
│ BY CATEGORY (Last 6 sprints): │
│ │
│ Dependencies: ████████████████ 35% │
│ Information: ██████████████ 30% │
│ Technical: ██████████ 20% │
│ Resources: █████ 10% │
│ Approvals: ██ 5% │
│ │
│ BY SOURCE: │
│ • DevOps team: 8 blockers (credential issues) │
│ • Design team: 6 blockers (spec delays) │
│ • External vendor: 4 blockers (API issues) │
│ │
│ RECURRING BLOCKERS: │
│ • API credentials (4 times) │
│ • Environment setup (3 times) │
│ • Unclear requirements (3 times) │
│ │
│ ACTION ITEMS: │
│ ✓ Create credential self-service for common APIs │
│ ✓ Improve environment automation │
│ ✓ Add requirements checklist to story template │
│ │
│ GOAL: Eliminate recurring blocker patterns │
└─────────────────────────────────────────────────────────────┘
Prevention
Proactive Strategies
BLOCKER PREVENTION:
┌─────────────────────────────────────────────────────────────┐
│ │
│ SPRINT PLANNING: │
│ • Identify dependencies before committing │
│ • Ensure dependent work is scheduled first │
│ • Get commitments from other teams │
│ • Flag high-risk items early │
│ │
│ REFINEMENT: │
│ • Ensure stories have all needed info │
│ • Identify external dependencies │
│ • Get design specs completed before sprint │
│ • Pre-request any needed access │
│ │
│ RELATIONSHIPS: │
│ • Build rapport with commonly-blocking teams │
│ • Establish cross-team communication channels │
│ • Share roadmaps to anticipate needs │
│ │
│ AUTOMATION: │
│ • Self-service for common requests │
│ • Automated environment provisioning │
│ • Pre-configured access for common resources │
│ │
│ BUFFERS: │
│ • Don't fill sprint to 100% capacity │
│ • Leave room for unexpected blockers │
│ • Have backup work ready │
└─────────────────────────────────────────────────────────────┘