Use Scope Change Management

Tom Mochal and Jeff Mochal

Chapter Chapter 11 in Lessons in Project Management, 2011, pp 45-48 from Springer

Abstract: Abstract There are two major reasons why projects have problems. The first is a basic lack of upfront definition and planning. The second is poor scope change management processes. Remember that scope refers to the box that defines the work of your project. High-level scope includes deliverables and boundary statements. The business requirements make up lower-level scope. Defining scope allows you to ensure you have an agreement with your sponsor on the box your project is responsible for. Defining scope also provides the baseline against which you can perform scope change management throughout the project.

Date: 2011
References: Add references at CitEc
Citations:

There are no downloads for this item, see the EconPapers FAQ for hints about obtaining it.

Related works:
This item may be available elsewhere in EconPapers: Search for items with the same title.

Export reference: BibTeX RIS (EndNote, ProCite, RefMan) HTML/Text

Persistent link: https://EconPapers.repec.org/RePEc:spr:sprchp:978-1-4302-3835-5_12

Ordering information: This item can be ordered from
http://www.springer.com/9781430238355

DOI: 10.1007/978-1-4302-3835-5_12

Access Statistics for this chapter

More chapters in Springer Books from Springer
Bibliographic data for series maintained by Sonal Shukla () and Springer Nature Abstracting and Indexing ().