The uncontrolled or inadequately governed expansion, shift, or accretion of project boundaries, objectives, requirements, or deliverables beyond the originally defined and authorised scope, occurring without formal change control or agreed redefinition of constraints.

Principle

When changes to objectives or requirements are introduced without formal governance (change control, budgetary approval, schedule revision), incremental additions accumulate and cause divergence between planned resources and actual demands, increasing schedule, cost, and quality risk.

Demonstration

Situation: A small public‑art commission specifies a single site‑specific installation and fixed delivery date. Recognition: During production, stakeholders request additional interactive features and a second installation without adjusting contract terms. Action: The team implements requests without formal change orders to avoid conflict. Consequence: Deadlines slip, budget is exceeded, and the original installation's coherence is weakened because resources were reallocated informally.

Misapplication

Error: Labeling every project change or client request as scope creep. Why plausible: changes often correlate with delays or overruns. Semantic error: conflating any change with uncontrolled expansion rather than distinguishing unauthorized, unmanaged additions from agreed, governed scope changes.

Consequence

Unmanaged scope expansion causally produces resource shortfalls, missed milestones, diminished quality, stakeholder friction, and potential contractual disputes because planning assumptions and resourcing remain unadjusted while demands grow.

Reversal

In exploratory, iterative, or research‑driven projects (e.g., experimental art practices, prototyping phases), iterative expansion may be an intended method for discovery; in those contexts, adding features under an agreed flexible framework is not scope creep but managed evolution.

Boundary

Clearly within: adding new deliverables or requirements without documented approval or budget/time reallocation. Boundary case: client requests that are reviewed and accepted with informal notes but without formal change control—whether this is creep depends on governance norms. Clearly outside: changes processed through formal change‑management and budget/schedule amendments.

Semantic Tension

Flexibility (responsiveness to new insights or stakeholder needs) versus control (predictability, budget and schedule discipline): resolving the tension requires explicit governance rules about which changes are permissible and how they are authorised.

Synthesis

Scope creep is defined less by the existence of change than by the absence of governance: managing boundaries requires procedures that convert legitimate evolution into authorised change and thereby prevent the cumulative drift that undermines project integrity.