What is scope creep and how can it be controlled?

• A. Uncontrolled expansion of project scope; controlled through change control, baselines, and rigorous scope management.
• B. Gradual refinement of requirements through stakeholder feedback.
• C. A change in project leadership without affecting scope.
• D. An increase in project budget without approval.

Answer: (A)

Scope creep is the uncontrolled expansion of the project scope, often happening when new work or requirements are added without proper authorization or adjustments to time and cost. The way to keep it in check is to use a formal change control process: every proposed change to scope is documented, analyzed for its impact on schedule, budget, and quality, and only approved by the appropriate authority before it’s included. Keeping a solid scope baseline—defined in the scope statement, the work breakdown structure, and requirements traceability—helps you spot and prevent unauthorized changes. Regular scope management practices, such as clear scope definition, a signed change request with impact assessment, and a change control board’s approval, ensure changes are deliberate and aligned with project goals. Also, avoid adding features beyond what was agreed unless a formal change is approved, because that’s what leads to creeping scope. The other options describe different situations: gradual refinement through stakeholder feedback can be managed within the scope framework, a leadership change doesn’t automatically alter scope, and a budget increase without approval is budget creep, not scope creep.