Which approach best manages changes to requirements approved during a project?

• A. Immediately implement all changes without documentation
• B. Require customer sign-off only, no internal approvals
• C. Update the project plan informally and proceed
• D. Through a formal change control process with updated SOW/contract amendments and impact assessments

Answer: (D)

Changes to approved requirements must be gatekept through a formal change control process. This provides a structured way to submit, analyze, and approve or reject changes before they are implemented. By conducting a formal impact assessment, you examine how the change affects scope, schedule, cost, quality, and risk, so you can decide if it’s worth pursuing and how to adjust the plan accordingly. Updating the statement of work or contract amendments formalizes the new terms with the customer, creating a legal and financial record that both sides agree to. This baseline discipline preserves control over the project and prevents uncontrolled shifts in direction or budget, which is essential for staying aligned with what was agreed and for maintaining clear accountability.

Implementing changes without documentation bypasses governance and invites scope creep and disputes. Requiring customer sign-off without internal approvals can ignore feasibility and risk implications. Informally updating the plan and proceeding lacks a defensible baseline and traceability, making it hard to track what changed and why.