Learn why dependency visibility gets harder, not easier, as the number of coordinating teams grows — and how a portfolio-level dependency tracker succeeds where a pile of team RAID logs fails. Build a single shared tracker that surfaces cross-team conflicts before they become blocked sprints.
Watch the free preview
Why dependency visibility breaks down as teams multiply — free to watch, no account needed.
What you'll learn
- Explain why dependency visibility degrades as the number of coordinating teams grows
- Distinguish a team-level RAID log from a portfolio-level dependency tracker
- Design the fields and workflow of a shared tracker that surfaces cross-team conflicts
- Manage dependencies in cadence through PI planning, Nexus and Scrum of Scrums
- Build a reusable Portfolio Dependency Tracker Template for a multi-team program
Syllabus
Why Dependencies Get Harder at Scale
Why dependency visibility breaks down as teams multiplyFree preview
What a dependency really is, and the cost of hidden ones
The Portfolio Dependency Tracker
Team RAID logs versus a portfolio dependency tracker
Designing the tracker — fields, ownership and workflow
Managing Dependencies in Real Programs
Managing dependencies in cadence — PI planning, Nexus and Scrum of Scrums
Case study — twelve teams, no shared view
Making Dependency Management Stick
Building your Portfolio Dependency Tracker Template
Common traps and anti-patterns to avoid