CAPM Practice: Explain when it is appropriate to use a predictive, plan-based approach

In predictive projects, baselines (scope, schedule, cost) are established at the end of planning before execution begins. These baselines represent the approved plan against which actual performance will be measured throughout the project. Setting baselines before execution provides the reference point needed for performance measurement and change control.

**Why not B:** Waiting until the first major deliverable is accepted is too late to set the baseline. Baselines must exist before execution begins so that performance can be measured from the start of work, not after significant deliverables are already completed.

**Why not C:** Demonstrating working software after each sprint is a characteristic of agile/adaptive approaches, not predictive. Predictive projects set baselines once during planning, not iteratively after each sprint cycle.

**Why not D:** Setting baselines at project closure defeats the purpose of baselines entirely. Baselines are reference points for measuring performance during the project; setting them after all work is complete would provide no value for performance management or change control.