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

In predictive projects, changes after baseline approval must go through integrated change control: a formal change request is submitted, the impact on scope, schedule, cost, and quality is analyzed, the Change Control Board (CCB) approves or rejects the request, and baselines are updated if approved. This process ensures changes are evaluated holistically before implementation.

**Why not B:** Implementing changes immediately without formal evaluation bypasses integrated change control. Even to maintain client satisfaction, significant changes must be assessed for their impact on scope, schedule, cost, and quality before implementation begins.

**Why not C:** Adding changes to a project backlog for the next iteration is an adaptive/agile practice, not a predictive one. In a predictive project at 60% completion, changes go through formal change control, not into an iteration backlog.

**Why not D:** Informing the client that no changes are possible is incorrect. Predictive projects can accommodate changes — they simply must go through formal integrated change control. Refusing changes entirely would be unnecessarily rigid and could damage the client relationship.