Scope creep

Scope creep – also known as feature creep – is the gradual, uncontrolled expansion of a project’s scope beyond its original boundaries — typically through the incremental addition of features, requirements, or objectives that were not part of the initial specification.

Individual additions are often small and seemingly reasonable in isolation, which is precisely what makes scope creep difficult to detect and resist. No single change appears to justify pushing back, yet the cumulative effect is a project that has grown significantly in size and complexity without a corresponding adjustment to budget, timeline, or resources.

Left unchecked, scope creep is a leading cause of project overruns, quality degradation, and delivery failures.

Scope creep can originate from multiple directions: clients or stakeholders who request additions after requirements have been agreed; internal teams who gold-plate features or add unsolicited improvements; and poorly defined initial requirements that leave room for ambiguous interpretation.

Effective mitigations include maintaining a clearly documented and agreed scope baseline, establishing a formal change control process through which new requests are evaluated and either deferred or traded against existing commitments, and practising [timeboxing] to create a natural boundary around what can be included in a given iteration.

The related concept of [software bloat] describes the downstream symptom in the delivered product, where accumulated scope creep results in software that is larger and more complex than its purpose requires.