Scope Creep
The uncontrolled expansion of product or project scope without corresponding decisions about value, cost, time, capacity, or risk.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/scope-creep/
01What it means
Scope creep is incremental growth in expected capabilities or work that occurs without explicit assessment and authorization of its consequences. It is not the same as all scope change: adaptive teams can change scope responsibly when they make tradeoffs visible and update expectations.[1][2]
02Why it matters
Small unexamined additions accumulate into delayed delivery, diluted outcomes, quality pressure, and hidden cost. Naming scope creep helps teams distinguish legitimate learning from commitments that expand without an accountable decision.
03When to use it
Use the term when work is being added outside an agreed decision process or without adjusting constraints. Do not use it to suppress customer evidence, necessary quality work, or responsible adaptation in an explicitly flexible scope.
04How it works
- Establish the relevant outcome, scope boundary, constraints, and decision rights.
- Capture proposed additions rather than absorbing them informally.
- Assess value, urgency, dependencies, risk, cost, and impact on existing commitments.
- Choose explicitly to add, exchange, defer, reject, or reframe the work.
- Update scope, plans, and stakeholder expectations when a change is accepted.
- Review recurring additions for unclear discovery, incentives, or governance.
05A practical example
During a mobile checkout redesign, stakeholders successively add loyalty enrollment, address verification, and receipt preferences without moving the launch date. The team surfaces their combined impact and exchanges the highest-value addition for a lower-priority item instead of silently absorbing all three.
06Where it breaks
The label can be abused to defend an obsolete plan or avoid learning. Some emergencies and compliance changes must alter scope, and flexible product teams may intentionally hold time and capacity stable while negotiating scope continuously.
Common mistakes
- Calling every evidence-based scope change scope creep.
- Accepting small additions because each seems harmless alone.
- Adding scope while pretending time, quality, and capacity are unaffected.
- Blaming requesters when decision rights and boundaries were unclear.
07Sources
- Three Proven Ways Business Analysts Help Prevent Scope CreepProject Management Institute · Professional conference paperThree Proven Ways Business Analysts Help Prevent Scope Creep
- Top Five Causes of Scope CreepProject Management Institute · Professional conference paperTop Five Causes of Scope Creep