What is the process for handling scope changes and change requests?

• A. Track scope changes informally and update the plan later.
• B. Capture via a formal change request, assess impact on scope, schedule, and cost, obtain approvals, and update plans.
• C. Changes must be approved by the entire project team.
• D. Update plans without approvals and inform stakeholders afterward.

Answer: (B)

Formal change control is the proper way to handle scope changes. When a change is proposed, it is captured in a formal change request that clearly describes what is being changed and why. The change is then analyzed for its impact on the project’s scope, schedule, and cost, so you can understand trade-offs, risks, and dependencies. After the impact is assessed, the appropriate authority—often a change control board or project sponsor—reviews and approves (or rejects) the change. Only after approval are the project plans, baselines, and related documents updated, and stakeholders are informed.

This approach prevents untracked scope creep and ensures everyone agrees on how the change will affect timelines and budgets. Implementing changes informally or without approvals can lead to misalignment and unmanaged risk, while trying to push updates with no governance or broad, unanimous team approval disregards established decision rights and slows progress.