What is a recommended process to manage scope creep in ERP deployment projects?

• A. Implement formal change control, document impacts, rebaseline schedules, secure approvals, and communicate changes to stakeholders.
• B. Implement only informal discussions and hope changes don't impact the timeline.
• C. Accept all requests without rebaselining until the project ends.
• D. Document changes at the end of the project only.

Answer: (A)

The question tests disciplined change control and governance over scope in ERP deployments. The best approach is to establish a formal change-control process that requires submitting a change request, assessing its impact on scope, timeline, and budget, documenting those impacts, and securing the appropriate approvals before any work proceeds. When a change is approved, the project baseline—schedule, cost, and scope—should be rebaselined to reflect the new reality, so plans stay accurate and achievable. Communicating the changes to all stakeholders is essential to maintain alignment, set clear expectations, and prevent surprises.

This approach prevents uncontrolled scope growth, ensures decisions are justified and traceable, and keeps everyone informed, which is far more reliable than relying on informal discussions, accepting changes without updating baselines, or delaying documentation to the end of the project.