Scope Creep in ERP Projects
Scope creep is the gradual expansion of project scope without formal approval or budget adjustment. It starts with small requests and ends with a project that runs months late and exceeds budget.
Scope creep is the most common cause of budget overruns in ERP projects. A formal change request process prevents small requests from growing into major delays.
Frequently Asked Questions
What is scope creep?
The gradual, unapproved expansion of project scope. Each individual change seems small, but the cumulative impact on budget and timeline is significant.
How do I prevent scope creep?
Define scope clearly in a project charter. Implement a formal change request process: every change is assessed on impact (time, cost, risk) before approval.
What if scope creep has already occurred?
Conduct a scope review with the steering committee. Explicitly choose what gets delivered now and what moves to a next phase.