Scope Creep: When 'Just One More Thing' Derails a Project
Scope creep is the slow, uncontrolled addition of work after a project starts. It happens when requirements aren't locked down, causing budget and schedule overruns. The footgun is thinking it can be eliminated; the real skill is managing it, not ignoring it.
Why it exists
Projects are planned in a moment in time, but executed over a period of time during which new ideas and needs emerge. Scope creep happens when these new requests are added to a project without a formal process to assess their impact on time and cost, causing uncontrolled growth.
The mental model
Think of scope creep as "kitchen sink syndrome." You start with a clear goal, like building a simple login page. Then someone asks to add social logins. Then another wants a complex password reset flow. Soon, you've added everything but the kitchen sink, and a simple task has become a massive, delayed epic.
How it works
Scope creep begins when a project's scope is not properly defined, documented, or controlled from the start. As work progresses, stakeholders make seemingly small requests for changes or additions. Without a process to vet these changes, they are approved and implemented, leading to a continuous expansion of the project's boundaries. In software, this is often called "feature creep." It is generally considered harmful, leading to cost and schedule overruns.
When to manage it
Scope creep is present in nearly every project and cannot be entirely prevented. The goal is to manage it, not eliminate it. If well-managed, scope creep can be beneficial. For example, adding a feature in response to a new market opportunity could create a much better final product. The key is controlled adaptation, not uncontrolled growth.
WHEN IT'S MOST HARMFUL Uncontrolled scope creep is destructive. It's most dangerous in projects with fixed budgets or tight schedules where there is no room to absorb the extra work. It leads to team burnout, missed deadlines, and blown budgets, endangering the entire project.
One canonical example
A project is scoped to create a basic internal reporting dashboard. As it's being built, a manager asks for an email export feature. Then another department asks for it to integrate with their separate CRM. Then an executive wants real-time mobile alerts. Each request seems reasonable in isolation, but together they derail the original timeline and budget, turning a straightforward project into a quagmire.
Interview question
What is the recommended strategy for dealing with scope creep in projects?
- a.Eliminate it entirely by enforcing strict, unchangeable requirements from the outset.
- b.Accept its presence as inevitable and focus on managing it through controlled processes.Correct
- c.View it as a sign of project failure and immediately re-evaluate the project's viability.
- d.Allow minor additions freely, as long as they don't significantly impact the budget.
Why? this is the answer
The card explicitly states that scope creep cannot be entirely prevented and the goal is to manage it, not eliminate it, through controlled adaptation. Option A is incorrect because the card highlights that new ideas and needs emerge, making strict prevention unrealistic and potentially detrimental.
Just read this? Test yourself on what you have been reading.
Read the original → en.wikipedia.org
- #project management
- #scope creep
- #feature creep
- #product management
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on project management — each one lists the topics its interview covers.
See open roles