A dependency exists when one team’s work relies on another team’s work or support. It can block progress or put a project timeline at risk, so teams need to make dependencies visible and coordinate expectations. section 9.2.3 section 11.4.2
Manage cross-team dependencies by:
- Clarifying project goals, milestones, deliverables, roles, communication channels, and update frequency. section 9.2.3
- Discussing timeline estimates, technical complexity, and resource availability with the teams involved. section 11.4.2
- Identifying tasks, such as API definitions or data modeling, that teams can do in parallel. section 11.4.2
- Documenting decisions and revised plans in shared project tools and follow-up communications. section 11.4.2
- When another team’s road map needs to change, explain the business value and propose collaborative options. section 3.2.4
A backend dependency
A frontend team cannot begin development until the backend team completes its work. The teams compare estimates, prioritize API definitions and data modeling for parallel work, and record their revised plan. section 11.4.2
A shared road map
A platform team modernizing promotions needs a royalty team’s expertise. It makes the case for combining the work with the royalty team’s planned system revamp. section 3.2.4
