Scope Creep
Scope creep is the uncontrolled expansion of project scope without corresponding adjustments to timeline, budget, or resources. It occurs when new requirements, features, or tasks are added incrementally — often through informal requests — without formal change control. It is the most common cause of projects finishing late and over budget.
Key Points
Scope creep is different from scope change — change goes through a formal process with documented trade-offs; creep does not
Warning signs: cards appearing without a corresponding change request, "quick adds" from stakeholders, growing task count with unchanged deadline
Prevention requires a baseline: document the agreed scope, and compare every new request against it
When creep is detected, the PM should present the trade-off: add this feature, but move the deadline by X days or cut feature Y
How Vizually.AI Uses This
On a Vizually.AI canvas, scope creep becomes visible when new cards appear outside the original zones or when the total card count exceeds the baseline snapshot. Take a canvas snapshot at project kickoff (the scope baseline). Periodically compare the current canvas to the baseline — new cards that weren't in the original snapshot are scope additions that should go through change control.