PMP Practice: Assess opportunities to deliver value incrementally

This scenario presents a project with characteristics that clearly favor a predictive approach: fully defined requirements locked by external regulation, a non-negotiable deadline, fixed scope mandated by compliance law, and integration with multiple legacy systems requiring careful planning and coordination. The regulatory framework provides complete requirements documentation, eliminating the uncertainty that would justify iterative discovery. The fixed deadline and compliance penalty for deviation make scope flexibility inappropriate. In this context, a predictive approach with comprehensive planning, detailed scheduling, baseline control, and structured milestone tracking is the most effective way to deliver business value with the required urgency. The approach ensures all regulatory requirements are addressed, dependencies across twelve legacy systems are managed, and the team can track progress against the immovable deadline. Business value in compliance projects is delivered by meeting the regulatory mandate on time and completely — not through early partial deliveries.

**Why not A:** This choice misapplies agile principles to an inappropriate context. While agile delivers value through iterative releases and welcomes changing requirements, this project has zero flexibility in requirements (they are regulatory mandates) and no opportunity for scope evolution. The compliance framework is complete and cannot change. Delivering partial functionality early provides no business value when the regulatory authority requires complete compliance by a specific date. This represents a common misunderstanding that agile is universally superior regardless of project characteristics.

**Why not C:** While hybrid approaches can be effective when project characteristics warrant them, this scenario lacks the conditions that make hybrid valuable. The requirements are not evolving, there is no benefit to incremental stakeholder feedback (the regulatory authority has already published all requirements), and the fixed deadline with compliance penalties makes iterative experimentation risky. Adding sprint ceremonies to a fundamentally predictive project creates process overhead without corresponding value. The team member's suggestion appears motivated by recent training rather than project needs.

**Why not D:** The project manager should select the appropriate methodology based on project characteristics, not organizational preference or sponsor opinion. The scenario provides clear indicators: documented requirements, regulatory mandate, fixed deadline, legacy system integration complexity, and zero scope flexibility. These factors make the methodology decision straightforward. Escalating this decision suggests the PM lacks the judgment to match approach to context, which is a core competency. The sponsor has already emphasized the non-negotiable deadline and locked scope, providing sufficient direction.