Skip to content
PMPHard

PMP Practice: Prepare the schedule based on methodology

Question 3 of 5 in Plan and Manage Schedule

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

Birch Tanaka is managing a sixteen-month pharmaceutical manufacturing plant construction project for Velvet Hippo Biologics. The project involves four major building phases, strict regulatory approvals at defined milestones, fixed contractual completion dates with penalty clauses, and coordination with three concurrent IT infrastructure projects using agile methodologies. During month three, the IT teams request that Birch's team adopt two-week sprints and iterative delivery to better synchronize dependencies. However, Birch's construction permits specify completion dates for foundation work, and her equipment vendors require twelve weeks advance notice for specialized HVAC system delivery. The CFO is concerned about budget predictability, and regulatory inspections are scheduled at fixed intervals tied to construction phase completeness. What approach should Birch take?
Show answer & explanation

Correct answer: Maintain the predictive schedule approach for the construction project while establishing formal integration points with the IT teams at predetermined milestones to manage cross-project dependencies

Explanation

This scenario presents a clear case where project characteristics dictate methodology selection. The construction project has fixed regulatory requirements, contractual penalty clauses, long procurement lead times, permit-driven completion dates, and a need for budget predictability—all hallmarks requiring a predictive approach. The IT projects are separate initiatives that happen to have dependencies. The best approach is to maintain the appropriate methodology for each project while creating structured coordination mechanisms at predetermined integration points. This respects the nature of each project type, maintains compliance and contractual obligations, and still enables effective cross-project coordination. The closing fact that regulatory inspections are tied to construction phase completeness makes it clear that sprint-based iterative delivery is incompatible with the project's fundamental constraints.

**Why not B:** This ignores fundamental project constraints. You cannot obtain regulatory approvals, meet permit deadlines, or manage twelve-week vendor lead times using two-week sprints. Construction phases must be complete for inspection—partial delivery of a foundation is not viable. This choice represents forcing a methodology based on organizational preference rather than project characteristics.

**Why not C:** While hybrid approaches can be effective, this option misapplies the concept. Using sprints internally while maintaining predictive milestones creates process overhead without benefit—the team would be planning in two conflicting cadences. The construction work itself has sequential dependencies and regulatory checkpoints that do not benefit from iterative cycles. This choice sounds sophisticated but adds complexity without addressing the actual need, which is cross-project coordination, not internal process change.

**Why not D:** This attempts to solve coordination by forcing other projects to change their approach. However, the IT projects may be well-suited to agile methodologies, and those teams are not under Birch's authority. Additionally, requesting three separate IT projects to change methodologies would create massive disruption. The coordination challenge should be solved through integration mechanisms, not by mandating uniform methodology across independent projects with different characteristics.

Key Concept

This question covers Prepare the schedule based on methodology under Plan and Manage Schedule (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