VS-08
Blocker Chain Length Exceeds Threshold
Value Stream Graph
Default severity: medium
PrioritizationProcessOutputRisk
What it detects
A blocking dependency chain has more links than the configured maximum — a chain of A blocks B blocks C blocks D of configurable depth means resolution requires multiple sequential unblocking events, making delivery timeline unpredictable.
Detection formula
FOR each_blocked_node B: blocker_chain_length = LENGTH(longest_blocking_path_to_unblocked_node) IF blocker_chain_length > config.graph.max_blocker_chain_length // default: 3 THEN FLAG deep_blocker_chain Report: full chain with node keys, owners, statuses, and agesExamples in practice
- Dependency links or initiative graph paths are missing, cyclic, or blocked.
- Downstream work waits on unresolved upstream dependencies.
- A team shows a blocking dependency chain has more links than the configured maximum while max blocker chain length is set to 3.
Suggested response
Repair dependency and initiative graph links so delivery paths and handoffs are explicit.
Coaching playbook
Symptom
A blocking dependency chain has more links than the configured maximum — a chain of A blocks B blocks C blocks D of configurable depth means resolution requires multiple sequential unblocking events, making delivery timeline unpredictable.
Why it matters
When "Blocker Chain Length Exceeds Threshold" keeps appearing, the team is signalling a repeatable process gap. Left unexamined, the pattern hides where work really stalls and makes improvement metrics harder to trust.
What you can achieve
Repair dependency and initiative graph links so delivery paths and handoffs are explicit.
Facilitation questions
- What system change would stop "Blocker Chain Length Exceeds Threshold" from firing again?
- What do the cited issues have in common — same root cause or same workaround?
- Who owns the two-week experiment and how will we verify on the next import?
Run this rule against your own tracker data with Flow Analyzer.