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

In predictive projects, the change management process requires formal change requests, analysis of impacts on scope/schedule/cost/quality, review by a Change Control Board (CCB), approval or rejection, and baseline updates. This disciplined process ensures changes are evaluated holistically and prevents unauthorized scope creep.

**Why not B:** Implementing changes without documentation violates integrated change control. Even after approval, changes must be documented with updated baselines, plans, and project records to maintain project governance, traceability, and accountability.

**Why not C:** Discussing changes in daily standups and incorporating them into sprints is an adaptive approach, not how predictive projects handle baseline changes. Predictive projects use formal change requests, impact analysis, and CCB approval rather than agile ceremonies.

**Why not D:** Allowing any team member to approve minor changes undermines change control governance. In predictive projects, changes to baselines require appropriate authorization levels — typically the project manager for minor changes and the CCB or sponsor for significant ones. Uncontrolled approvals lead to scope creep.