Skip to content

Glossary · Scope creep

What is scope creep?

Scope creep is work growing after it was agreed without the deadline or effort changing with it.

In practice

It arrives as extra edge cases, more polish and “1 small thing.” No single request looks unreasonable. 15 small yeses can turn 2 weeks into a quarter.

Scope creep isn't the same as deliberately changing your mind. A change is a decision. Creep happens when nobody makes one.

Why it matters for product builders

Write down what is out of scope. A named exclusion is harder to add back quietly.

What changes in AI-first products

The cost of adding scope fell faster than the cost of owning it. An agent may build the extra case in an afternoon, making “yes” feel harmless.

Maintenance, explanation and eventual removal still accumulate. AI changes the first invoice, not the lifetime cost.

**Source note**

The [PMBOK definition](https://www.pmi.org/learning/library/top-five-causes-scope-creep-6675) describes scope creep as adding features and functionality without addressing the effects on time, costs and resources, or without customer approval.

See how Annsa does it: Done When →

Sources

  1. Larson and Larson, PMI Global Congress 2009Top five causes of scope creep ... and what to do about them

    Quotes the PMBOK Guide, "adding features and functionality (project scope) without addressing the effects on time, costs, and resources, or without customer approval".

Last reviewed 2026-08-21

Put it to work with your agents.

Begin with one agent and the work that matters next.