Scope Creep
Scope creep is the uncontrolled expansion of a project's deliverables or requirements beyond what was originally agreed, usually without a corresponding adjustment to budget or timeline.
In short
- Uncontrolled expansion of a project's deliverables beyond what was agreed.
- Usually happens incrementally -- one small addition at a time, not a single dramatic change.
- Rooted in vague deliverable language, missing acceptance criteria, or no change-control process.
- Erodes margins, blows through timelines, and creates friction between the parties.
Where it comes from
A client asks for "just one more" feature, a stakeholder assumes something was included that wasn't explicitly excluded, or vague deliverable language gets interpreted more broadly by one side than the other intended. It's a documentation problem before it's a project-management problem.
How to prevent it
Four defenses: precise, testable deliverable definitions; explicit exclusions (what is not included, not just what is); a defined acceptance-criteria process for each deliverable; and a change-control clause requiring any scope addition to go through a written, priced amendment first.
How ScopeWise checks this
ScopeWise's Scope agent is built to catch the root causes before signature -- vague deliverable language, missing acceptance criteria, absent change-control process -- rather than waiting to catch the symptom after a project is already underway.