VS-12
Parallel Delivery Opportunity Missed
Value Stream Graph
Default severity: medium
PrioritizationProcessOutputRisk
What it detects
Two or more branches of the delivery graph are independent (no shared dependencies between them) but are being worked on sequentially by the same squad — parallelism is available but not being used. Identifies where WIP limit increase or team splitting could accelerate delivery.
Detection formula
FOR each_squad S: active_issues = issues WHERE assignee.squad = S AND status IN active FOR each_pair (A, B) IN active_issues: IF NO path exists between A and B in G (neither direction) THEN independent_pair — track count IF COUNT(independent_pairs) > config.graph.parallel_opportunity_threshold // default: 3 THEN FLAG serialised_parallel_work Recommend: which pairs could run concurrentlyExamples in practice
- Dependency links or initiative graph paths are missing, cyclic, or blocked.
- Downstream work waits on unresolved upstream dependencies.
- A team shows two or more branches of the delivery graph are independent (no shared dependencies between them) but are being worked on sequentially by the same squad while parallel opportunity threshold is set to 3.
Suggested response
Repair dependency and initiative graph links so delivery paths and handoffs are explicit.
Coaching playbook
Symptom
Two or more branches of the delivery graph are independent (no shared dependencies between them) but are being worked on sequentially by the same squad — parallelism is available but not being used. Identifies where WIP limit increase or team splitting could accelerate delivery.
Why it matters
When "Parallel Delivery Opportunity Missed" 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 "Parallel Delivery Opportunity Missed" 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.