Project Management Best Practice 2 – Define What is Not In Scope

All project managers know one of the greatest risks to the on-time, on-budget completion of their project is scope creep; the gradual expansion of functionality, broadening in organizational application, and/or increase in quality requirements often without a commensurate increase in project resources or duration. Subsequently, project managers strive to clearly define their project’s scope in order to defend against scope creep. But when doing so, they often forgo an invaluable tool; defining what is outside their project’s scope.

Hi there! Gain access to this article with a StrategyDriven Insights Library – Total Access subscription or buy access to the article itself.

Related content from StrategyDriven

 

Common Overlooked Controllable Human Resources Costs

Customer, Influencer, and Coach Avatars

Common Overlooked Controllable Supply Chain and Inventory Management Costs

Protocols for Responding to Black Swan Events