Scope Creep

Scope Creep is the progressive and often uncontrolled expansion of a project’s scope beyond what was initially defined. New requirements, specification changes and additional features accumulate without a corresponding adjustment to budget and timelines.

How it works #

In a software project, scope creep typically starts with seemingly small requests: “let’s add this field too”, “it would be useful to have this function as well”. Each individual change seems reasonable, but the cumulative effect is devastating. Specifications become a moving target, the team can never reach a stable baseline, and the project enters an endless cycle of revisions.

What it’s for #

Recognising scope creep is the first step to preventing it. Defence mechanisms include: formal change requests with impact analysis, specification freezes per phase, rigorous prioritisation and the ability to say “no” — or at least “not now”.

When to use it #

The term describes a project management anti-pattern to avoid. In large consulting projects, scope creep often becomes a weapon in the supplier’s hands: incomplete specifications justify delays and additional costs, turning a fixed-scope project into an open-ended engagement.