Scaled Agile Workshop: Dependency Mapping
Keeps multi-team releases honest: visualizing queues, WIP agreements, and reconciliation checkpoints without heavyweight portfolio layers.
Request informationOverview
Scaled choreography fails when teams optimize locally. We model a three-team release train with simulated blocking bugs and platform upgrades, then rehearse escalation paths that do not turn into executive fire drills. Participants learn to differentiate dependency types—technical, staffing, and policy—and choose appropriate resolution forums. Includes a reusable Miro / whiteboard starter built from neutral shapes only (no numeric dashboards in slides).
What is included
- Dependency typology cards with collaboration verbs
- Simulated cross-team bug swarm
- Cadence map for planning, refinement, and system demo
- Runbook for rotating dependency sheriffs
- Reflection on tool notifications fatigue
Outcomes
- Host a dependency forum that finishes under 45 minutes
- Draft a cross-team WIP policy with explicit queue caps
- Explain when to pause feature starts without blaming individuals
FAQ
Tooling requirements?
We demo Miro patterns but practices map to physical boards as well.
Prerequisite experience?
At least six months working adjacent to another engineering team is advised.
What is out of scope?
We do not implement portfolio investment scoring; this is throughput collaboration.