PMP · Question #921
A project manager is working on a project that is using a hybrid approach. One key input for the deliverable will be from the outcome of another project that is using an agile approach. What should…
The correct answer is C. Align with the other project manager's high-level project time lines. When a hybrid project relies on an outcome from an agile project, the project manager should align high-level timelines to manage dependencies and integrate deliverables effectively.
Question
A project manager is working on a project that is using a hybrid approach. One key input for the deliverable will be from the outcome of another project that is using an agile approach. What should the project manager do next?
Options
- AParticipate in the other project's daily standup meetings.
- BAsk the other project manager to change the delivery methodology.
- CAlign with the other project manager's high-level project time lines.
- DRequest that the other project manager develop a work breakdown structure (WBS).
How the community answered
(26 responses)- A4% (1)
- B12% (3)
- C81% (21)
- D4% (1)
Why each option
When a hybrid project relies on an outcome from an agile project, the project manager should align high-level timelines to manage dependencies and integrate deliverables effectively.
Participating in daily standups might provide too much detail and not be the most efficient way for a hybrid project manager to manage a high-level dependency with another project.
Forcing another project to change its methodology is generally not feasible or productive, as it could disrupt their project and is outside the project manager's direct authority.
In a hybrid environment, especially when integrating with an agile project, understanding and aligning on key milestones and high-level timelines is crucial for managing dependencies and ensuring the overall project schedule remains feasible. This allows the hybrid project manager to anticipate when the agile deliverable will be ready and plan their project's next steps accordingly, enabling effective integration of outputs.
Requesting a Work Breakdown Structure (WBS) from an agile project manager is inappropriate as agile projects typically use backlogs and user stories, not WBS, for planning and tracking work.
Concept tested: Managing dependencies in hybrid/multi-methodology projects
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/agile-practices
Topics
Community Discussion
5
Ingrid P.May 4, 2026C is the answer here. In a hybrid setup your planning still needs some baseline dates for dependencies, and the agile side exposes those through release and iteration timelines rather than a full WBS. Option D is a trap because you cannot force a predictive artifact onto an agile project, and A would just add noise without giving you the commitment point you actually need. I made a card for this one with the cue "hybrid PM needs agile input" on the front and "align on high-level timelines, not WBS or standup attendance" on the back, and I tagged it for a 14
Samuel O.May 19, 2026I first leaned toward A figuring I should just get myself into their standups to track progress, but that is not my meeting to crash and it does not solve the dependency planning. C is the practical move because in a hybrid setup you need their high-level timelines to anchor your delivery dates, and asking an agile team to build a WBS or switch methodologies would never fly.
Mei-Ling H.May 28, 2026Saw this on my exam last month, the word high-level is the clue for C.
Dervla O.Apr 24, 2026B. Agile inputs break hybrid schedules, so push for consistent methodology.
Samuel O.Apr 24, 2026Actually C is the right call here. In practice you do not force one methodology on every team, you adapt the schedule to accommodate both predictive and iterative work streams, which is exactly what hybrid project management is designed to handle.