PMP · Question #74
During iteration planning, team A identifies that an important deliverable is dependent upon a deliverable from team B. What should the project manager do?
The correct answer is B. Inform team B of the dependency and ensure that the deliverable is planned. When an agile team identifies an inter-team dependency, the project manager must ensure the dependent deliverable is recognized and planned by the other team.
Question
During iteration planning, team A identifies that an important deliverable is dependent upon a deliverable from team B. What should the project manager do?
Options
- AAsk team B to focus on their backlog and deliver based on their priority
- BInform team B of the dependency and ensure that the deliverable is planned
- CMake team A a part of team B and ensure that the deliverable is ready
- DRequest team B to immediately start this activity and deliver to team A
How the community answered
(44 responses)- A5% (2)
- B73% (32)
- C16% (7)
- D7% (3)
Why each option
When an agile team identifies an inter-team dependency, the project manager must ensure the dependent deliverable is recognized and planned by the other team.
This approach ignores the dependency, potentially causing delays for Team A, and does not align with collaborative agile principles where dependencies must be actively managed.
In agile, inter-team dependencies are critical to manage. The project manager should facilitate communication between Team A and Team B, making Team B aware of the dependency and working with them to integrate the dependent deliverable into their own iteration plan, ensuring alignment and timely completion to prevent delays.
Merging teams or forcing team A into team B is an extreme measure that disrupts team autonomy and structure, and it is not a standard or efficient way to manage a dependency.
Requesting immediate action from Team B without proper planning can disrupt their current iteration, priorities, and workflow, which is contrary to agile practices of sustainable pace and organized planning.
Concept tested: Managing inter-team dependencies in agile
Source: https://www.pmi.org/pmbok-guide-standards/foundational/agile-practice-guide
Topics
Community Discussion
5
Grace U.Nov 27, 2025B is right here. The PM's job is to surface the dependency and make sure team B factors it into their planning, not to reorder their backlog or merge the teams.
Wei W.Dec 13, 2025B is right, but who actually coordinates cross-team dependencies in your org, the PM or the teams themselves?
Wesley A.Dec 6, 2025Failed my first attempt partly because I kept trying to force other teams to change their priorities instead of just communicating dependencies. B is correct here because the PM should inform team B so they can plan the deliverable into their iteration, not dictate their priorities or restructure the teams. Anyone know if the exam treats this differently when both teams report to different release train engineers versus the same PM?
Lena V.Dec 7, 2025Same RTE or different RTE, the exam answer stays B, but if they are on different release trains you escalate dependency conflicts through the RTEs rather than expecting team B to selfmanage a crosstrain commitment.
Lena V.Dec 20, 2025B is correct but the wording is softer than what youd see on the job. D is the trap because it sounds proactive, but you dont get to reprioritize another teams backlog by fiat in agile, you negotiate dependencies and make sure they get planned into the iteration.