Scope Creep
The uncontrolled expansion of a project's scope after work has begun, typically through new requirements, expanded features, or shifting goals. Unlike feature creep which affects the product broadly, scope creep happens within a specific initiative or sprint.
Scope creep is one of the primary causes of missed deadlines and budget overruns in software development. It happens when stakeholders add just one more thing during development, when edge cases discovered during implementation trigger expanded requirements, or when initial assumptions prove wrong and the team expands scope instead of simplifying the approach. Clear acceptance criteria, firm sprint commitments, and empowered product owners are the primary defenses.
AI development is highly prone to scope creep because model behavior in edge cases often triggers additional requirements. A team building an AI classifier discovers during development that the model struggles with a specific input category, leading to an expanded data collection effort that was not in the original scope. Growth teams can mitigate scope creep by defining minimum success criteria upfront: the AI feature must handle the top 80% of cases correctly, with graceful degradation for the remainder. Shipping the constrained version, measuring impact, and then expanding scope based on data prevents the project from growing indefinitely in pursuit of perfection.
Related Terms
Product-Market Fit
The degree to which a product satisfies strong market demand. Achieving product-market fit means customers are actively seeking, using, and recommending your product because it solves a real and pressing problem for them.
Jobs to Be Done
A framework that defines customer needs as functional, emotional, and social jobs people hire products to accomplish. It shifts focus from demographic segments to the underlying progress customers are trying to make in specific circumstances.
Minimum Viable Product
The simplest version of a product that can be released to test a core hypothesis with real users. An MVP delivers just enough functionality to gather validated learning while minimizing development time and cost.
Minimum Lovable Product
An evolution of the MVP concept that emphasizes delivering enough quality and delight that early users genuinely love the product. It balances speed-to-market with the emotional engagement needed to drive organic word-of-mouth growth.
Design Sprint
A five-day structured process for rapidly prototyping and testing ideas with real users. Developed at Google Ventures, it compresses months of debate into a focused week of mapping, sketching, deciding, prototyping, and testing.
Lean Startup
A methodology for developing businesses and products through validated learning, rapid experimentation, and iterative releases. It emphasizes reducing waste by testing assumptions before building fully-featured solutions.