Scope creep

From apppm
Revision as of 09:41, 22 September 2017 by S130038 (Talk | contribs)

Jump to: navigation, search

Contents

Abstract

The following article describes the project management phenomenon scope creep. The definitions of project scope and product scope as well as scope creep are discussed. Scope creep can happen both in proportion to project and product scope. Product scope creep can happen both naturally and when a stakeholder demands a new feature of the product. Project scope creep can happen when a project team is taken a new working direction with a project - both intentionally and unintentionally. Natural changes will happen in project all the time, and a project rarely delivers exactly what was asked for on day 1 of the project. The key to avoid scope creep is to handle these changes carefully, so this article also discusses tools to avoid scope creep. Suggestions on how to handle scope creep is also given, if this is unavoidable.


[1] [2] [3] [4] [5] [6]

What is scope?

What is scope creep?

How to avoid scope creep

How to handle scope creep

Is scope creep always bad?

Conclusion

References

  1. Monnappa, A. (2017) Project Scope Management: What It is and Why It’s Important. SimpliLearn
  2. Maylor, H. (2010) Project Management, Fourth Edition. Harlow, England: Pearson Education Limited
  3. Clark, T. (2014) How to Manage Scope Creep - and Even Prevent It From Happening. The LiquidPlanner Blog
  4. Danish Standards Foundation. (2012) ISO 21500 Guidance on Project Management, First Edition. Charlottenlund, Denmark: Dansk Standard
  5. Duke, P. Scope Creep, the Killer of Projects. Entrepreneur
  6. Keifer, S. C. (1996) Scope creep … not necessarily a bad thing. PM Network, 10(5), 33-35


Annotated Bibliography

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox