Skip to content
PMPCAPM

Scope Creep

Scope creep is the uncontrolled expansion of project scope without adjustments to time, cost, and resources, typically occurring when changes are made without going through integrated change control.

Share:

Know it well enough for the exam? Questions on Scope Creep are scenario-based, not definitional.

Practice it free

Explanation

Scope creep is one of the most common and damaging risks in project management. It occurs when new features, requirements, or work are added to the project without corresponding changes to the schedule, budget, or resources. Unlike approved scope changes that go through integrated change control, scope creep happens informally and without proper authorization.

Scope creep often begins with small, seemingly harmless additions. A stakeholder asks for "just one more feature," or a team member adds extra functionality they believe would be helpful. Over time, these incremental additions accumulate, leading to schedule delays, cost overruns, resource exhaustion, and potential project challenges. The root causes often include poor requirements gathering, weak change control processes, unclear scope boundaries, and stakeholder pressure.

Preventing scope creep requires a clear scope statement with explicit exclusions, a robust change control process, consistent use of the requirements traceability matrix, and strong stakeholder engagement. When change requests arise, they should be formally evaluated for impact on scope, schedule, cost, quality, risk, and resources before any decision is made.

Key Points

  • •Uncontrolled expansion of scope without adjustments to time, cost, or resources
  • •Occurs when changes bypass integrated change control
  • •Often starts small but accumulates into significant project impact
  • •Prevented through clear scope definitions and robust change control

Exam Tip

Scope creep is unauthorized change. Gold plating is adding extra features by the team. Both are problems, but they have different sources. Know the distinction for the exam.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Burndown Chart

A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Power Interest Grid (Power/Influence Grid)

The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.

Critical Path Method (CPM)

The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Part of

Scope Management

Study full domain →

Practice Scope Creep

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.