PMP Practice: Develop, execute, and validate a strategy for stakeholder engagement

This government infrastructure project has characteristics that strongly favor a predictive approach: a fixed-price contract with milestone-based payments, quarterly regulatory compliance checkpoints, multi-county coordination requirements, and strict documentation needs. These constraints create a low-tolerance environment for scope or schedule changes. In predictive projects with complex stakeholder landscapes, the project manager should systematically categorize stakeholders based on their power, influence, interest, and impact, then create a structured engagement plan that aligns with the contractual milestones and regulatory timeline. This ensures stakeholders receive appropriate information at the right times while maintaining the discipline needed for compliance and contract management. The scenario's emphasis on competing priorities, regulatory checkpoints, and fixed payments makes structured stakeholder categorization and planned engagement the most appropriate approach.

**Why not B:** While agile sprint reviews work well for projects with evolving requirements and flexible scope, this project operates under a fixed-price contract with regulatory compliance checkpoints that require predictive planning and documentation. The two-week sprint cadence would conflict with quarterly regulatory reviews and milestone-based payments, creating administrative overhead without delivering value given the project's constraints.

**Why not C:** Although hybrid approaches can be effective, this scenario does not indicate that community engagement requires iterative cycles or that the community's needs are uncertain enough to warrant an adaptive approach. The project's regulatory, contractual, and multi-jurisdiction coordination requirements all point toward a single, coherent predictive approach. Introducing hybrid complexity without clear justification would add unnecessary risk to stakeholder management.

**Why not D:** Methodology selection is a project management decision based on project characteristics—not a stakeholder vote. The contract type, regulatory requirements, and organizational constraints have already determined that a predictive approach is appropriate. Asking stakeholders to vote on methodology would create confusion about project management authority and could lead to selections that conflict with contractual obligations and organizational governance.