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:

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 is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

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.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Schedule Performance Index (SPI)

Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.

Earned Value Management (EVM)

Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.

Power/Influence Grid

The power/influence grid is a stakeholder classification model that groups stakeholders based on their level of authority (power) and their active involvement or ability to affect the project (influence).

Part of

Scope Management

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.