CAPM Practice: Demonstrate an understanding of the various project life cycles and processes

In a predictive project with established scope, budget, and timeline, changes should be managed through a formal change control process. This process allows the project manager to assess the impact of requested changes on all project constraints (scope, time, cost, quality, resources, and risk) before making decisions. This is the appropriate first step to handle change requests professionally.

**Why not A:** Rejecting the request outright is inappropriate. Even in a predictive project with fixed scope, changes can be considered — they simply need to go through the formal change control process for proper evaluation of impacts before a decision is made.

**Why not B:** Immediately working on the new features bypasses the change control process. Without proper impact assessment, the team risks scope creep, budget overruns, and schedule delays. All changes must be formally evaluated first.

**Why not D:** Switching to an adaptive approach mid-project is not the first step. The established change control process exists specifically to handle change requests in a predictive environment. A methodology change would itself be a major decision requiring careful consideration.