Comprehensive and Detailed Explanation From Exact Extract:
Scope creep occurs when additional work, features, or requirements are added to a project without proper evaluation, approval, or changes to time, cost, or resources. The most effective way to prevent scope creep is to define the scope clearly in the project plan and use that definition as a scope baseline to control changes.
A clear scope in the project plan includes:
A project scope statement that describes what is included and what is excluded.
A work breakdown structure (WBS) that decomposes work into defined deliverables.
A scope baseline against which all change requests are evaluated.
A formal change control process to review, approve, or reject scope changes.
Why the other options are incorrect:
B. Adding extra features to improve satisfaction – Adding features without proper approval is a direct cause of scope creep.
C. Allowing minor scope changes without review – Even small changes, if unmanaged, accumulate and change the project’s scope, cost, and timeline.
D. Including new scope requests during the project – New scope may be appropriate, but only after formal review and approval, not automatically.
Therefore, defining the scope clearly in the project plan (and managing against it) is the method that helps prevent scope creep, making A the correct answer.
[Reference:Information Technology Management Study Guide – Project Management: Scope Planning, Scope Baseline, and Change Control., , , ]
