Skip to content
PMPMedium

PMP Practice: Determine Critical Information Requirements

Question 7 of 15 in Develop an Integrated Project Management Plan

Pick an answer below — you'll get the explanation instantly, no signup.

Naledi Dlamini is the project manager for Silver Badger Diagnostics, a biotech startup developing a new diagnostic device. The product roadmap includes both regulatory compliance milestones (which require detailed documentation and sequential approvals) and user interface design iterations (which benefit from rapid prototyping and customer feedback). The executive sponsor, Yuna Park-Hashimoto, wants the project delivered in 14 months to meet a critical industry conference deadline. During initial planning discussions, the engineering team insists on using a waterfall approach for hardware development due to manufacturing constraints, while the software team strongly prefers two-week sprints with continuous deployment. The quality assurance lead warns that mixing methodologies could create integration bottlenecks. Naledi has not yet documented how these different work streams will be coordinated. What should Naledi do MOST effectively to address this situation?
Show answer & explanation

Correct answer: Design a hybrid delivery approach that specifies how predictive and adaptive components will integrate, including coordination points and shared governance mechanisms

Explanation

This scenario tests the project manager's ability to assess project complexity and design an appropriate integrated delivery approach when different work streams have legitimately different needs. The hardware development has valid constraints requiring predictive planning (manufacturing tooling, regulatory documentation), while the software work genuinely benefits from iterative delivery. The best response is to intentionally design a hybrid approach that explicitly addresses how these streams will coordinate — defining integration points, establishing shared governance for cross-stream dependencies, clarifying decision rights, and ensuring visibility across both predictive and adaptive components. This tailors the delivery model to the actual project needs rather than forcing artificial uniformity. The project management plan must document these coordination mechanisms to prevent the integration bottlenecks the QA lead identified.

**Why not A:** Mandating a single methodology for all teams ignores the legitimate differences between hardware and software work streams. Forcing agile on hardware development with manufacturing constraints would create problems, while forcing predictive planning on software would limit the team's ability to iterate. One-size-fits-all undermines effectiveness.

**Why not B:** Building consensus on a single unified methodology has the same fundamental flaw as mandating one approach. Even if the team reaches consensus, a single methodology cannot effectively serve both the hardware team's manufacturing constraints and the software team's need for rapid iteration. The QA lead's concern about integration bottlenecks requires explicit coordination mechanisms, not methodology uniformity.

**Why not C:** Escalating to the sponsor for a methodology decision abdicates the project manager's responsibility for delivery planning. The scenario states Naledi has not yet documented how work streams will be coordinated, which is her role to define. The sponsor should not be deciding delivery methodology when the PM has the expertise and context to design the appropriate approach.

Key Concept

This question covers Determine Critical Information Requirements under Develop an Integrated Project Management Plan (Process).

Share:

This is 1 of 100 free PMP questions

Unlock 6,300+ PMP practice questions with detailed explanations, progress tracking, and exam readiness prediction.

Unlock All Questions