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.
|Subscribe to the StrategyDriven Insights Library
Sign-up now for your StrategyDriven Insights Library – Total Access subscription for as low as $15 / month (paid annually).
Not sure? Click here to learn more.
|Buy the Article
Don’t need a subscription? Buy access to Project Management Best Practice 2 – Define What is Not In Scope for just $2!
FREE related content from StrategyDriven