As you have learned, SCOPING a project is pivotal in defining a project so that detailed planning can be done. SCOPE can also be one of the negotiables when a call for project duration reduction is necessary ("something's gotta give!", as they say). Reduction of scope can be accomplished in various ways such as taking out features that are nice to have vs "must-have", limiting a software implementation to one site, and others you may have seen in your own experience. BUT, what about Scope CREEP? How does that happen and why? In some cases, it can lead to total project failure. Watch the video below and discuss the following:

TheWASA- a true story of scope creep

https://www.youtube.com/watch?v=kmJ59yyYza4

• Why was the WASA project a failure?
• What could the project manager have done to manage the project better?
• Share an example of another project that had scope creep (it could be one where you were involved as a team member or a stakeholder, or from your research). What was the nature of this scope creep/cause? What was the effect of this scope creep on the project you described, such as an increase in cost or project duration if any?