Plan and prioritise · Add-on
Manage dependencies with other teams
In a larger organisation, your plan often depends on other teams' work. Find those dependencies early, agree them in writing and review them often.
About 2-5 daysEvergreenLast reviewed 5 November 2026
Who this applies to
- Skills it builds
- Delivery and executionCommunication and influence
- PM types
- All
- Product types
- All
- Starting points
- All
- Ways of working
- All
- Experience
- All
- Size of organisation
- EstablishedLarge enterprise
Steps, by experience
Beginner (under 1 year)
- List the work you need from other teams to deliver your plan.
- Meet each team to agree what, when and who owns it.
- Record each dependency with a date and an owner.
- Review the list every week.
- Raise a slipping dependency early, with options.
Intermediate (1 to 4 years)
- Map dependencies in both directions: what you need and who needs you.
- Agree interfaces and dates in writing.
- Plan around high-risk dependencies, for example with a simpler first release.
Experienced (5+ years)
- Spot dependency patterns across teams and fix the cause, such as team boundaries.
- Run a regular cross-team planning session.
- Escalate systemic blockers to leadership with data.
Who can do this
Owner: Product manager
Can be delegated to
- Delivery Manager or Scrum Master: Keep the dependency list up to date
- Tech Lead or Architect: Agree technical interfaces with other teams
Reviewed by: Delivery Manager
Tool examples
- Jira
- Link issues across projects to show dependencies.
- Miro
- Draw a dependency map for planning sessions.
Definition of done
- Dependencies listed with owners and dates
- Agreements written down
- Weekly review in place
Common pitfalls
- Agreeing dependencies verbally
- Finding them at the end of the plan
- Escalating without options
If you lead the team
What good looks like: Dependencies on other teams are found early, agreed and tracked.
Ask your PM
- Which other teams do we depend on, and have they committed?
- What happens if a dependency slips?
Warning signs
- Dependencies are found mid-build.
- Agreements are verbal and forgotten.