Handling Blocked Tasks | Keep Work Flowing
Manage blocked tasks to maintain velocity. GitScrum's blocker tracking and dependency visualization help identify impediments and prioritize resolution.
5 min read
Blocked tasks silently kill team velocity and create cascading delays. GitScrum's blocker tracking, dependency visualization, and notification systems help teams quickly identify impediments, communicate status to stakeholders, and prioritize resolution to keep work flowing smoothly.
Common Blocker Types
| Type | Example | Resolution Path |
|---|---|---|
| Dependency | Waiting for API from Team B | Cross-team coordination |
| Information | Requirements unclear | Product Owner clarification |
| Technical | Environment not working | DevOps/Infrastructure |
| Access | Need permissions | IT/Admin request |
| External | Third-party API down | Vendor escalation |
| Approval | Design sign-off needed | Stakeholder follow-up |
Blocker Management Process
BLOCKER LIFECYCLE
1. IDENTIFY & MARK
┌─────────────────────────────────────────────────┐
│ Developer realizes task is blocked │
│ │
│ Action: │
│ • Mark task as "Blocked" immediately │
│ • Document specific blocker │
│ • Note what's needed to unblock │
│ • @mention relevant people │
└─────────────────────────────────────────────────┘
│
▼
2. COMMUNICATE
┌─────────────────────────────────────────────────┐
│ Visibility to team and stakeholders │
│ │
│ Channels: │
│ • Daily standup mention │
│ • Slack/Teams blocker channel │
│ • Direct message to resolver │
│ • Sprint board visibility │
└─────────────────────────────────────────────────┘
│
▼
3. ESCALATE (if needed)
┌─────────────────────────────────────────────────┐
│ Timeline: │
│ • 24 hours: Scrum Master aware │
│ • 48 hours: Management escalation │
│ • 72 hours: Executive attention │
│ │
│ Based on impact and urgency │
└─────────────────────────────────────────────────┘
│
▼
4. RESOLVE & DOCUMENT
┌─────────────────────────────────────────────────┐
│ When blocker cleared: │
│ • Update task status │
│ • Document resolution │
│ • Continue work │
│ • Note prevention ideas │
└─────────────────────────────────────────────────┘
Blocker Documentation Template
BLOCKED TASK DOCUMENTATION
┌─────────────────────────────────────────────────┐
│ Task: GS-456 - Implement payment flow │
│ Status: 🚫 BLOCKED │
│ │
│ ───────────────────────────────────────────── │
│ │
│ BLOCKER DETAILS: │
│ Type: External Dependency │
│ Description: Waiting for Stripe webhook │
│ endpoint documentation │
│ │
│ BLOCKED SINCE: Jan 15, 2025 (2 days) │
│ │
│ NEEDED TO UNBLOCK: │
│ • Stripe webhook payload examples │
│ • Error handling documentation │
│ │
│ ACTION TAKEN: │
│ • Contacted Stripe support (ticket #12345) │
│ • Asked in developer forum │
│ • @pm to escalate if no response by EOD │
│ │
│ ASSIGNEE CAN WORK ON: │
│ • GS-457 (unrelated task) in meantime │
└─────────────────────────────────────────────────┘
Sprint Board Visibility
BLOCKER VISIBILITY ON BOARD
┌────────────┬───────────┬──────────┬───────┐
│ To Do │ In Prog │ Blocked │ Done │
├────────────┼───────────┼──────────┼───────┤
│ │ │ │ │
│ [Task 1] │ [Task 3] │ [Task 5] │[Done 1│
│ │ │ 🚫 2 days │ │
│ [Task 2] │ [Task 4] │ │[Done 2│
│ │ │ [Task 6] │ │
│ │ │ 🚫 1 day │[Done 3│
│ │ │ │ │
└────────────┴───────────┴──────────┴───────┘
BLOCKED COLUMN:
• Separate column makes blockers visible
• Shows duration blocked
• Forces daily attention
• Prevents hidden delays
Blocker Metrics
BLOCKER TRACKING METRICS
SPRINT 12 BLOCKER ANALYSIS:
┌─────────────────────────────────────────────────┐
│ │
│ Total tasks blocked: 8 │
│ Total blocked time: 42 hours │
│ Avg resolution time: 5.25 hours │
│ │
│ BY TYPE: │
│ ├── External dependency: 3 (18 hrs) │
│ ├── Information needed: 2 (8 hrs) │
│ ├── Technical issue: 2 (12 hrs) │
│ └── Approval waiting: 1 (4 hrs) │
│ │
│ PATTERN IDENTIFIED: │
│ External dependencies from Team B causing │
│ 50% of blocked time. Discuss in retro. │
│ │
└─────────────────────────────────────────────────┘
Best Practices
Anti-Patterns
✗ Waiting silently for blockers to resolve
✗ Not marking tasks as blocked (hidden delays)
✗ No escalation path defined
✗ Same blockers recurring without systemic fix
✗ Developer stopping all work when one task blocked
✗ Blaming instead of problem-solving