Uncontrolled growth of a project's scope after work has started, usually because the scope was never properly defined in the first place.
No documented coiner. The nearest dated relatives are 'creeping featuritis', recorded in the Jargon File v2.1.1 of 12 June 1990, and 'mission creep', in print from 1993.
// Where it sits
Scope creep is very often a definition failure discovered late, rather than a discipline failure discovered early.
What it really means
The word scope comes from Greek skopos: a target, a mark to aim at.
Which makes scope creep a nearly perfect piece of accidental etymology — the target moving while you shoot at it. And it locates the fault where it usually belongs: scope creep is diagnosed during delivery as a discipline problem, and is very often a definition problem from before delivery. Scope that was never adequately defined cannot be defended, because there is nothing precise enough to defend.
The vocabulary around it has fragmented usefully, and the distinctions are worth keeping because they point at different culprits.
Scope creep — the job itself grows. Usually client-side, arriving as a run of small, entirely reasonable requests.
Feature creep — the narrower case, where what keeps arriving is features. It can cause scope creep, but they are not the same thing, and knowing which you have determines what you do next.
Gold plating — and this is the one worth flagging, because it inverts the blame. Gold plating is unrequested polish added by the team, past the point of diminishing returns. Nobody asked for it. It feels like craftsmanship. It consumes the same budget as scope creep and no change-control process will catch it, because there is no request to control.
Kitchen-sink syndrome — not a separate failure but another name for scope creep itself: everything goes in.
The practical consequence of separating these is that they have different remedies. Scope creep is answered by change control: a process for saying yes, and here is what it costs. Gold plating is answered by a definition of done — because the person doing it is not being difficult. They are trying to do good work, and nobody has told them where the finish line is.
Megaprojects are especially prone to it: the longer and larger the build, the more chances the target has to move.
Where it comes from
The original sense of 'scope' is a TARGET — which is precisely what creeping destroys. The etymology contains the whole problem.
Myths & misconceptions
Scope creep and feature creep are the same thing.
When defined separately, scope creep is enlargement of the project's SCOPE while feature creep is specifically the addition of extra FEATURES. Feature creep can cause scope creep; they are not identical, and conflating them hides which one you have.
All unrequested extra work is scope creep.
Gold plating is the distinct case where the TEAM adds unrequested polish past the point of diminishing returns. Scope creep typically originates client-side. Same symptom, opposite culprit — and opposite remedy.
Compare & contrast
Scope creep vs gold plating
Same symptom, opposite culprit. The client widens the scope; the team widens the polish. Change control fixes one of these and has no effect at all on the other.
| // | Scope creep | Gold plating |
|---|---|---|
| Originates with | The client | The team |
| Requested | Yes | No |
| Fixed by | Change control | Definition of done |
| Feels like | Being imposed on | Doing good work |
How it connects
- Mission Creepthe parent metaphor, and the more serious failure.
- Bikesheddingthe other named way a team spends effort on the wrong thing.
Tell it apart
Questions people ask
- What causes scope creep?
- Scope that was inadequately defined, documented or controlled before work began. It is usually diagnosed as a discipline problem during delivery and is very often a definition problem from before delivery.
- How is it different from gold plating?
- Gold plating is unrequested enhancement added by the team. Scope creep is growth of the agreed scope, usually client-driven. Different culprits, different fixes.
- Does it affect big projects?
- Notably so — most megaprojects are recorded as falling victim to it, which suggests the problem scales faster than the controls do.