Standard : Blocked Time per Work Item

Description

Blocked Time per Work Item measures the duration a work item remains in a blocked or impeded state while it is in progress. This highlights how often and how long items are delayed due to unresolved dependencies, approvals, unclear scope, or unavailable resources.

Tracking blocked time helps teams reduce friction, remove systemic blockers, and improve flow. It also brings attention to where cross-team or organisational constraints may be limiting delivery efficiency.

How to Use

What to Measure

  • Identify when a work item enters a blocked state (e.g. flagged in the board or tagged in the workflow).
  • Record when the item becomes unblocked and resumes progress.
  • Track total blocked time per item, and aggregate per sprint or month for patterns.

You can also track:

  • Frequency of blocked items
  • Average blocked duration
  • % of cycle time spent blocked

Formula

Blocked Time = Unblock Date – Block Date

To assess flow health:

% Time Blocked = (Blocked Time / Cycle Time) x 100

Instrumentation Tips

  • Enable blocked/unblocked tagging or statuses in your tracking tool (e.g. Jira, Azure DevOps).
  • Use automation or comments to timestamp block/unblock events.
  • Maintain a blocker log to capture common causes and systemic trends.
  • Visualise blocked work separately in boards and reports.

Benchmarks

There are no strict benchmarks, but typical patterns include:

Metric Healthy Range
Avg Block Duration < 1–2 days
% Items Blocked (per sprint) < 15–20%
% Cycle Time Blocked < 10–15%

Trends are more valuable than absolute thresholds. Use internal baselines to assess improvement.

Why It Matters

  • Reveals friction in delivery
    Blockers often reflect process bottlenecks, unclear scope, or organisational dependencies.

  • Supports continuous improvement
    Helps identify recurring themes that can be addressed systemically.

  • Enables proactive intervention
    Real-time blocked tracking prompts quicker collaboration and issue resolution.

  • Improves transparency
    Provides visibility into hidden delays that are often not captured in traditional cycle metrics.

Best Practices

  • Flag blocked items visually and make them part of daily stand-up rituals.
  • Track and analyse blocked time per item to uncover repeat issues.
  • Categorise blockers (e.g. external dependency, waiting for decision, tech issue).
  • Review blockers in retrospectives to agree action plans.
  • Set expectations around escalation and unblock timeframes.

Common Pitfalls

  • Not tagging or timestamping blockers consistently.
  • Treating blockers as individual failures rather than system signals.
  • Allowing long-blocked work to accumulate and stall WIP.
  • Ignoring the compounding cost of frequent short blockers.

Signals of Success

  • Reduction in average and total blocked time per sprint.
  • Teams escalate and resolve blockers quickly and collaboratively.
  • Recurring blockers are documented and addressed systemically.
  • Blocked work is discussed openly without blame, enabling learning.
  • [[Cycle Time per Work Item Type]]
  • [[Work Item Age]]
  • [[Flow Efficiency]]
  • [[Queue Time Between Workflow Stages]]

Aligned Industry Research

  • Accelerate (Forsgren et al.)
    Encourages eliminating organisational bottlenecks to improve software delivery performance.

  • Lean Software Development (Poppendieck & Poppendieck)
    Highlights delays and waiting as a key form of waste in value delivery.

  • Kanban Method (David J. Anderson)
    Uses blocker clustering to reveal system design problems and improve flow stability.