PMP Practice: Prioritize tasks based on business value

This scenario presents a project with characteristics that strongly favor a predictive approach: fixed regulatory requirements (FDA approval), approved specifications that cannot change, sequential construction dependencies, secured capital funding with defined scope, and legally binding permits and contracts already in place. The business value is delivered through compliant, on-time completion of the facility expansion within the FDA approval window—not through incremental feature delivery or scope adaptation. The project manager should respectfully explain why the project's nature, constraints, and contractual commitments make the planned predictive approach most appropriate, then execute accordingly. Changing approaches would introduce unnecessary risk to regulatory compliance, contractor agreements, and the critical timeline. The team members' suggestion, while well-intentioned, reflects a misunderstanding of when iterative approaches add value versus when they introduce complications.

**Why not A:** Scheduling a workshop on agile benefits and transitioning to sprints ignores the project's regulatory, contractual, and sequential constraints. FDA-approved specifications, finalized building permits, and fixed-price contractor agreements cannot be managed iteratively. Advocating for agile in this context demonstrates a misunderstanding of when adaptive approaches add value.

**Why not B:** Escalating to the sponsor for a methodology decision is unnecessary when the project's characteristics clearly dictate the appropriate approach. The PM should exercise professional judgment and explain why predictive planning fits this specific project rather than asking the sponsor to resolve a methodology question the PM can answer.

**Why not C:** Adopting a hybrid approach where construction is predictive but software integration is iterative sounds reasonable but is not supported by the scenario. The scenario describes a facility expansion with FDA approval constraints, not a software development project. There is no indication that any component would benefit from iterative delivery.