VS-11
Cross-Tribe Dependency Without Agreed Handoff Date
Value Stream Graph
Default severity: medium
PrioritizationProcessOutputRisk
What it detects
A dependency link crosses tribe boundaries but the dependent issue has no due date or target date on the blocking issue — there is no agreed delivery commitment from the supplying tribe, making the dependent tribe\'s planning impossible. cross_tribe_deps = \[(A, B)
Detection formula
FOR (A, B) IN G.edges WHERE A.tribe != B.tribe AND edge_type = dependency\] FOR each (dependent, blocker) in cross_tribe_deps: IF field_value(blocker, config.content.target_date_fields) IS NULL THEN FLAG missing_cross_tribe_sla Report: dependent_issue, dependent_tribe, blocker_issue, blocker_tribeExamples in practice
- Dependency links or initiative graph paths are missing, cyclic, or blocked.
- Downstream work waits on unresolved upstream dependencies.
- A team shows a dependency link crosses tribe boundaries but the dependent issue has no due date or target date on the blocking issue while target date fields is set to Configured per workspace.
Suggested response
Repair dependency and initiative graph links so delivery paths and handoffs are explicit.
Coaching playbook
Symptom
A dependency link crosses tribe boundaries but the dependent issue has no due date or target date on the blocking issue — there is no agreed delivery commitment from the supplying tribe, making the dependent tribe\'s planning impossible. cross_tribe_deps = \[(A, B)
Why it matters
When "Cross-Tribe Dependency Without Agreed Handoff Date" 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 "Cross-Tribe Dependency Without Agreed Handoff Date" 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.