Feature creep, also called scope creep when applied to a whole project, is the tendency for a product's requirements to keep expanding after work has begun. Each addition may seem small and reasonable, but together they delay delivery, raise cost and make the product harder to use and maintain.
Why it matters
More features are not automatically more value. Every feature must be designed, built, tested, documented, supported and kept working as the product evolves, which adds to technical debt. Teams guard against creep with a clear product requirements document, a prioritised backlog, an MVP mindset and a change-request process in which new asks are weighed against time and cost.
Example
Original scope: monitor a URL and send an email alert (4 weeks)
Week 2: "Can we add SMS?"
Week 3: "And Slack, and a mobile app?"
Week 6: nothing shippedHandled well, the SMS and Slack ideas go to the backlog for a later release.
Common mistakes
- Saying yes to every request from a single loud stakeholder or customer.
- Having no written scope to point to.
- Ignoring the maintenance cost of each addition.
- Blaming clients, when unclear scope at the start is often the cause.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.