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

Change control decisions in predictive projects weigh benefits against impacts. A change that improves the product must be evaluated against its effect on scope, schedule, cost, and risk. If the cost and schedule impact is acceptable and the benefit justified, the Change Control Board may approve it. If the impact is too large relative to the benefit, it may be deferred to a future project phase or release.

**Why not A:** Whether the requesting stakeholder is on the critical path is irrelevant to change control decisions. Change requests are evaluated based on their impact to project baselines, not on the requester's position in the schedule network.

**Why not B:** Whether similar changes were rejected on previous projects has no bearing on the current change decision. Each change request must be evaluated on its own merits and its specific impact on the current project's scope, schedule, cost, and risk.

**Why not C:** The project manager's personal preference about a change is never a valid factor in change control. Decisions must be based on objective analysis of impacts and benefits, not subjective opinions.