Watched the recorded video? Learn how to claim PDU credit here.


Project managers, executive stakeholders, program managers, anyone with a PMP credential


We all agree that scope creep is one of the major contributors to project failure. The problem is that too often management sees the responsibility for scope management to be the sole responsibility of the project manager. In reality, managing scope is the responsibility of everyone on the project team, including the customer.

Inadvertent scope increases can easily occur - team members don't truly understand the deliverables, requirements aren't clearly spelled out, team members subjectively add features that weren't asked for, or someone is just doing a favor for someone. Scope creep doesn’t happen because someone purposefully wanted to add scope to the project.

So how do we give project team members the necessary tools to effectively combat the urges to inadvertently increase scope?

We need a mindset of process improvement throughout the organization and discipline to manage them across all stakeholders.

This month we are going to discuss a simple and effective way to discuss the impacts of scope creep to your stakeholders and provide simple tools to get every project team member in tune with the costs of their actions.


  • Get your stakeholders and project team on board
  • Create an effective process improvement across organization
  • Provide simple tools to avoid project scope

Updated on: