In project management, you will need to come up with strategies to manage scope creep. When you allow scope creep, it can cause a ripple effect of other problems including, delayed completion, overspending, and not accomplishing the original goal of the project. 

Scope creep is bound to happen; whether it’s a construction project or an IT project. It’s when seemingly insignificant tasks get grouped in with project requirements after the project scope has been established. 

To maintain the integrity of the project, there are a few ways to ensure that the project stays on track. 

Scope should be clearly defined at the beginning.

Defining the scope at the beginning of the project is a foundational step that cannot be overlooked.

The scope is usually outlined in detail on the statement of work (SOW). It can also be found on the project charter in a more high level view. 

Manage scope creep by ensuring all stakeholders are aware and in agreement with the scope before beginning the project.

~A best practice as a project manager is to require a signature of approval on the requirements and anything additional will need to be reviewed and approved.

Establish a process for change control. 

Another way to manage scope creep is by establishing a change control process that addresses any possible impact to the project scope, budget, and schedule.

Doing this helps to level-set with stakeholders. So there’s a clear path forward and no surprises in cases where there are significant impacts to scope, budget and schedule. 

It’s important to note the difference between planned and unplanned changes on a project.

Scope creep happens when planned changes or additions are added during the project.

Unplanned changes are a direct result of an unanticipated set of conditions; things we may not have control over. 

Having solid change management helps maintain the stability of the project.

Document all risks and decisions.

Documentation is King in project management. You can manage scope creep by keeping track of all risks and decisions.

Usually kept on a RAID log, any change or discussion that could impact the project should be documented and referred back to in order to keep everyone accountable. 

Create a detailed project plan.

Your project plan is your bible. It gives you step by step instructions on how to complete the project.

Your timeline is set to specific tasks and you have the order in which each task is to be completed and by whom.

Basically… if it’s not on the plan it’s likely not happening.

To manage scope creep effectively, first refer to your SOW, then your change log, and finally your project plan.

Keep as much detail in your project plan as possible and ensure your plan is updated after noting any approved changes.    

Frequent communication with team and stakeholders. 

Manage scope creep by keeping everyone informed. Communicate with stakeholders as frequently as you need to.

Long story short, CYA at all times. If you don’t know what CYA is, google it.

Each time your project documents are updated with budget, scope, and schedule changes, communicate the changes with stakeholders so everyone’s on the same page. 

By, Airess Rembert, PMP, Member of Women Of Project Management & Blogger at The Nerd Bae

Join.

Join the full discussion inside the Women Of Project Management Membership. Listen to part of our conversation on the Women Of Project Management Podcast.

If you're new to our community, Women Of Project Management is the only community created to support & amplify the voices of women & women of color in every specialty of the project management industry worldwide. We support women in every stage of their career, learn more at Women Of Project Management.