Skip to content
PMPMedium

PMP Practice: Break Down Scope

Question 14 of 14 in Develop and Manage Project Scope

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

Putri Wulandari is managing a regulatory compliance upgrade for Amber Raven Consulting, a pharmaceutical manufacturer. The project must implement new FDA data integrity standards across four manufacturing sites by a fixed regulatory deadline in 14 months. The scope includes validating 23 existing systems, upgrading hardware at two sites, and implementing standardized documentation procedures. Regulatory requirements are fully defined in published FDA guidance documents, and any scope changes require formal regulatory impact assessment and potentially amended submissions to the FDA. During project planning, a senior stakeholder suggests switching to an iterative delivery approach with two-week sprints to 'increase flexibility and team engagement.' The stakeholder argues this would allow the team to respond faster to emerging issues. Which approach would be most appropriate for obtaining stakeholder agreement on project scope?
Show answer & explanation

Correct answer: Develop a detailed scope baseline with formal change control, explaining that the fixed regulatory requirements and compliance validation needs make a predictive approach more suitable

Explanation

This scenario requires a predictive approach because the scope is fully defined by external regulatory requirements, changes trigger formal regulatory processes, and the work involves compliance validation with fixed acceptance criteria. When regulatory compliance drives the project, stakeholder agreement on scope means establishing a detailed scope baseline with formal change control mechanisms. The project manager should explain why the project characteristics—fixed regulatory deadline, fully defined requirements, formal validation protocols, and regulatory change impacts—make a predictive approach the right fit. Simply adopting stakeholder preferences without considering project constraints would expose the organization to compliance risk. The PM's responsibility is to recommend the appropriate methodology based on project context and help stakeholders understand why it serves the project's success.

**Why not B:** Scheduling a workshop to democratically vote on methodology prioritizes team preferences over project constraints. Methodology selection should be based on project characteristics, regulatory requirements, and organizational context—not popularity. A vote cannot change the fact that fixed requirements and formal compliance validation demand a predictive approach.

**Why not C:** A hybrid approach where requirements gathering is iterative but validation follows a sequential process is unnecessary because requirements are already fully defined in published FDA guidance documents. Iterative requirements gathering adds no value when the scope is fixed by regulation. It would introduce unnecessary complexity and delay without improving outcomes.

**Why not D:** Adopting an iterative approach with two-week sprints because it will improve team morale and responsiveness ignores the fundamental project constraints. The regulatory requirements cannot change, scope changes require formal regulatory impact assessments, and the work involves compliance validation with fixed acceptance criteria. Morale benefits do not justify a methodology mismatch that could jeopardize regulatory compliance.

Key Concept

This question covers Break Down Scope under Develop and Manage Project Scope (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