Scope Creep: When 'Just One More Thing' Derails a Project
Scope creep is the uncontrolled growth of a project's requirements after it starts. It shows up as 'small tweaks' that balloon into major features, delaying schedules and increasing costs. The footgun is trying to prevent it entirely instead of managing it.
WHY IT EXISTS Projects are a balance of scope, time, and cost. When the scope isn't rigorously defined and defended from the start, it naturally expands as new ideas or overlooked requirements surface mid-project. This uncontrolled growth is scope creep.
THE MENTAL MODEL Think of scope creep as "kitchen sink syndrome." You start with a clear goal, like building a simple sink. Then someone suggests adding a garbage disposal. Then a hot water dispenser. Then a soap pump. Each is a seemingly small addition, but soon your simple, on-budget project is complex, over-budget, and behind schedule.
HOW IT WORKS Scope creep manifests as a series of seemingly minor requests or additions after a project's initial plan is approved. Without a formal process to evaluate these changes against the project's budget, timeline, and goals, they get incorporated one by one, leading to continuous, uncontrolled growth. This is also called feature creep or requirement creep.
WHEN TO USE IT While scope creep is generally harmful, not all changes are bad. A well-managed change control process allows a team to evaluate a new requirement. If it genuinely improves the final product and its impact on cost and schedule is understood and approved by all stakeholders, it's a deliberate strategic decision, not creep.
WHEN NOT TO USE IT Unmanaged scope creep is always dangerous. It thrives when the project scope is poorly defined from the start, or when there is no process for handling change requests. Letting every 'small' request slide without assessment is a recipe for blown budgets, missed deadlines, and team burnout.
ONE CANONICAL EXAMPLE A team is tasked with building a simple user login page with an email and password field. Mid-project, a stakeholder asks to add 'Login with Google.' Then another asks for 'Login with Facebook.' A developer then decides to add a 'Forgot Password' flow that wasn't planned. Each addition on its own seems reasonable, but together they derail the original timeline and effort estimate for the simple login page.
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.