Scope creep occurs as what, and how is it managed?

Scope creep occurs as what, and how is it managed?

• A. Controlled changes to project scope with formal approvals.
• B. A steady, planned expansion of scope without checks.
• C. Uncontrolled changes to project scope; manage with formal change control and clear requirements.
• D. Scope creep only occurs in software maintenance, not development.

Answer: (C)

Scope creep means the project starts to grow beyond what was originally agreed, with new features or requirements added after the scope has been defined and approved, often without formal evaluation. This can lead to delays, budget overruns, and strained resources because work is being done that wasn’t planned for. The best way to handle it is through a formal change-control process paired with clear, well-documented requirements from the start. A formal process captures every change request, analyzes its impact on scope, schedule, and cost, and requires approval before any change is incorporated. Once approved, the scope baseline, schedule, and budget are updated and stakeholders are informed, keeping the project aligned and under control. This approach emphasizes preventing unapproved shifts and ensures only necessary, properly evaluated changes are added. The other options describe either planned changes, or changes without checks, or limitations to software projects, which don’t accurately describe how scope creep arises or is best managed.

Scope creep means the project starts to grow beyond what was originally agreed, with new features or requirements added after the scope has been defined and approved, often without formal evaluation. This can lead to delays, budget overruns, and strained resources because work is being done that wasn’t planned for. The best way to handle it is through a formal change-control process paired with clear, well-documented requirements from the start. A formal process captures every change request, analyzes its impact on scope, schedule, and cost, and requires approval before any change is incorporated. Once approved, the scope baseline, schedule, and budget are updated and stakeholders are informed, keeping the project aligned and under control. This approach emphasizes preventing unapproved shifts and ensures only necessary, properly evaluated changes are added. The other options describe either planned changes, or changes without checks, or limitations to software projects, which don’t accurately describe how scope creep arises or is best managed.