According to the PMBOK® Guide and the Agile Practice Guide, the choice of methodology is dictated by the stability of the requirements and the flexibility of the baselines.
Predictive (Traditional/Waterfall) Characteristics: The key indicators in this scenario are that the baselines have been approved and there is minimal ability to vary them. In a predictive approach, the scope, schedule, and cost are determined early in the project life cycle. Any changes to these baselines typically require formal change control.
Parallel Phases: While predictive projects are often thought of as purely sequential, the PMBOK® Guide notes that phases can be overlapped (fast-tracked) or run in parallel to compress the schedule, provided the requirements are well-understood.
Minimal Variance: The " minimal ability to vary the baselines " is the hallmark of a predictive environment. Unlike adaptive or iterative models where the plan is expected to evolve, a predictive approach seeks to manage the project against a fixed plan to ensure high levels of certainty and control.
Analysis of other options:
Option A: An Incremental approach delivers functional portions of the project in parts. While it uses fixed baselines for each increment, it is usually focused on frequent delivery of working products rather than parallel phases with rigid, unvarying baselines for the whole project.
Option C: A Hybrid approach combines predictive and adaptive elements. Since this scenario emphasizes " minimal ability to vary " and does not mention any adaptive or agile components, " Predictive " is a more accurate fit.
Option D: An Iterative approach focuses on repeating activities until the product is " correct. " It explicitly allows for—and expects—the baselines to vary and evolve as the team learns more through each cycle.
Per PMI standards, a methodology characterized by pre-approved, rigid baselines with restricted change during execution is defined as a Predictive approach.
