PMP Practice: Obtain Stakeholder Agreement on Scope

This scenario requires a hybrid approach that tailors scope management to each component's characteristics. The compliance module has fixed regulatory requirements, a non-negotiable deadline, and documented legal specifications — all characteristics that favor predictive scope definition with detailed requirements and formal change control. The analytics dashboard has evolving user preferences, a need for experimentation, and flexible timing — characteristics that favor adaptive scope management with a prioritized backlog and iterative delivery. A hybrid approach allows the project manager to apply the most effective scope management strategy to each component based on its nature, rather than forcing a single methodology across incompatible work streams. This maximizes both regulatory compliance certainty and business value discovery.

**Why not B:** While adaptive approaches offer flexibility, the compliance module's fixed regulatory requirements and non-negotiable deadline make predictive scope management more appropriate for that component. Applying adaptive methods to work with firm regulatory constraints would introduce unnecessary risk and could jeopardize compliance.

**Why not C:** While predictive planning suits the compliance module, forcing the analytics dashboard into comprehensive upfront planning would eliminate the intended benefit of iterative refinement based on user feedback. This approach sacrifices business value discovery for unnecessary rigidity in a component where requirements are expected to evolve.

**Why not D:** Deferring the scope approach decision creates unnecessary delay and risk when the project characteristics already clearly indicate which approach suits each component. The compliance module's regulatory deadline requires immediate predictive planning to ensure timely delivery, and waiting for velocity data is irrelevant to choosing the appropriate scope management method.