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.
Read the original → en.wikipedia.org
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.