Scope Creep is the stuff Project Management nightmares are made of. Project Managers don’t like scope creep because it makes the project and everything that goes with it (budget, resources, client expectations, timeline, etc.) utterly unpredictable. 

What is Scope Creep? 

PMI defines scope creep as ‘Adding additional features or functions of a new product, requirements, or work that is not authorized (i.e., beyond the agreed-upon scope).’

But as much as we would like to avoid it, scope creep is part of the project management package. Every project knows scope creep on some level. There is no getting away from it. The question is, if you can’t avoid it, how do you manage it best and what can you do about it when it strikes? 

Scope creep occurs when small changes are made to a project that appear not to be worth an official discussion. The problem is that a lot of small changes can have a big effect. The longer a project takes, the more room there is for scope creep. Worst-case scenario, it can cause a project to fail. 

How to stop Scope Creep from ruining your Project? 

So what are our top tips to avoid scope creep spinning out of control?