What is Dependency Management?
Dependency management is the process of identifying work that cannot start or finish until another team, system, or deliverable is ready. In product development, dependencies are the most common source of missed deadlines.
A dependency exists whenever Team A cannot ship Feature X until Team B delivers Component Y. The PM's job is to surface these connections early, negotiate timelines, and create contingency plans when things slip.
Why Dependency Management Matters
Dependencies kill roadmaps silently. A PM who plans a Q2 launch without knowing that the platform team is rebuilding the auth system in Q2 will discover the conflict too late. By then, commitments are made and stakeholders are expecting delivery.
At scale, dependency management becomes the primary job of senior PMs and program managers. Companies like Google and Amazon have found that cross-team coordination costs grow exponentially with org size.
How to Manage Dependencies
Map dependencies at the start of each planning cycle. For each initiative on your roadmap, ask: what do we need from other teams, and what do other teams need from us?
Create a simple dependency matrix: columns for your initiatives, rows for other teams. Mark each cell as "none," "input needed," or "blocking." Share this with stakeholders during planning.
Assign an owner to each critical dependency. The owner's job is to check in weekly and escalate early if timelines shift.
Dependency Management in Practice
Amazon uses "two-pizza teams" specifically to minimize dependencies. Each team owns its full stack, reducing the need for cross-team coordination. When dependencies exist, they are formalized as API contracts with SLAs.
Spotify's squad model handles dependencies through "chapter" meetings where engineers from different squads align on shared platform work, and through quarterly planning sessions where squads flag cross-squad needs.
Common Pitfalls
- Discovering dependencies mid-sprint. Always map dependencies during sprint planning, not after work begins.
- Assuming other teams share your priorities. Their roadmap is not your roadmap. Negotiate timelines explicitly.
- No escalation path. When a dependency is at risk, there should be a clear process to raise the issue before it becomes a blocker.
- Over-reliance on a single person. Knowledge dependencies on one engineer are the riskiest kind. Document and cross-train.
Related Concepts
Dependency management ties closely to release management and sprint planning. It is a core skill in stakeholder management and directly impacts roadmap reliability. For large orgs, see product ops.