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

Iteratively updating the project plan based on weekly team feedback is characteristic of adaptive, not predictive approaches. Predictive plans are established upfront and changes are managed through formal change control. Iterative planning, sprint feedback loops, and continuous replanning are adaptive concepts.

**Why not A:** Formal change control is a defining characteristic of predictive projects. Changes to baselines must go through a structured process of evaluation, approval, and documentation. This is core to the predictive approach, not something that contradicts it.

**Why not B:** Comprehensive upfront requirements definition is fundamental to predictive methodology. The predictive approach assumes requirements can be fully understood and documented before work begins, enabling detailed planning of scope, schedule, and cost.

**Why not D:** Sequential delivery following a defined plan is inherent to the predictive approach. Work flows through phases in order — from initiation through planning, execution, and closing — with deliverables produced according to the predetermined plan.