When requirements change mid-project, what is the recommended sequence of actions?

When requirements change mid-project, what is the recommended sequence of actions?

• A. Initiate change control, re-evaluate scope and impact, communicate changes, adjust plan, rebaseline.
• B. Ignore changes and continue as planned.
• C. Reassign blame to team members and escalate.
• D. Cancel the project and start a new initiative.

Answer: (A)

When requirements change mid-project, manage it through formal change control. Start by capturing the change request and initiating the change control process, then perform an impact analysis to understand how the change affects scope, schedule, cost, quality, and risks. After evaluating the impact, communicate the implications to stakeholders and obtain approval before proceeding. If approved, update the project management plan and other baselines, then rebaseline to reflect the new direction. This approach keeps work aligned with approved objectives, maintains governance, and prevents uncontrolled scope changes. Ignoring the change, blaming others, or canceling the project when a change arises would undermine alignment, accountability, and value delivery.

When requirements change mid-project, manage it through formal change control. Start by capturing the change request and initiating the change control process, then perform an impact analysis to understand how the change affects scope, schedule, cost, quality, and risks. After evaluating the impact, communicate the implications to stakeholders and obtain approval before proceeding. If approved, update the project management plan and other baselines, then rebaseline to reflect the new direction. This approach keeps work aligned with approved objectives, maintains governance, and prevents uncontrolled scope changes. Ignoring the change, blaming others, or canceling the project when a change arises would undermine alignment, accountability, and value delivery.