What is scope creep and how can it be prevented?

• A. Gradual expansion of project scope due to changing requirements without approvals.
• B. Immediate termination of project upon budget overruns.
• C. Designating new vendors mid-project.
• D. Gradual expansion of project scope beyond agreed terms; prevented by strict change control processes.

Answer: (D)

Scope creep is the gradual expansion of project scope beyond what was originally agreed, often driven by new or changing requirements that are added without formal approval. This unchecked growth can push out timelines, inflate costs, and strain resources because the baseline plan isn’t updated to reflect the changes.

The best description ties this expansion to a preventive approach: strict change control processes. By requiring that every proposed change is documented, analyzed for its impact on scope, schedule, and budget, and then reviewed and approved by stakeholders, the project keeps scope within agreed bounds. This formal mechanism prevents casual or unauthorized additions from slipping in and ensures everyone stays aligned.

Inner details help: when changes are approved, you adjust the plan and baselines; when they’re not, you reject or defer them. Choices like terminating a project due to budget overruns or bringing in new vendors mid-project describe different management concerns and aren’t definitions of scope creep. The prevention aspect highlighted here—change control—addresses the root cause by controlling how scope can change.