A Guide to Project Management

Been incurred or committed etc is collected as part

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: ope Verification--formalizing acceptance of the project scope. 5.5 Scope Change Control--controlling changes to project scope. These processes interact with each other and with the processes in the other knowledge areas as well. Each process may involve effort from one or more individuals or groups of individuals, based on the needs of the project. Each process generally occurs at least once in every project phase. Although the processes are presented here as discrete components with welldefined interfaces, in practice they may overlap and interact in ways not detailed here. Process interactions are discussed in detail in Chapter 3. In the project context, the term scope may refer to: Product scope--the features and functions that characterize a product or service. Project scope--the work that must be done to deliver a product with the specified features and functions. The processes, tools, and techniques used to manage project scope are the focus of this chapter. The processes, tools, and techniques used to manage product scope vary by application area and are usually defined as part of the project life cycle (the project life cycle is discussed in Section 2.1). A project generally results in a single product, but that product may include subsidiary components, each with its own separate but interdependent product scopes. For example, a new telephone system would generally include four subsidiary components--hardware, software, training, and implementation. Completion of the project scope is measured against the project plan, but completion of the product scope is measured against the product requirements. Both types of scope management must be well integrated to ensure that the work of the project will result in delivery of the specified product. Project Project Management Management Body of Body of KnowledgeE L KnowledgeE PL MP AM SA S A Guide to the Project Management Body of Knowledge (PMBOK Guide) 2000 Edition 2000 Project Management Institute, Four Campus Boulevard, Newtown Square, PA 19073-3299 USA NAVIGATION LINKS ACROYMNS LIST ACRONYMS LIST 51 ACROYMNS LIST Chapter 5--Project Scope Management Figure 51 | | PROJECT SCOPE MANAGEMENT 5.1 Initiation .1 Inputs .1 Product description .2 Strategic plan .3 Project selection criteria .4 Historical information .2 Tools and Techniques .1 Project selection methods .2 Expert judgment .3 Outputs .1 Project charter .2 Project manager identified/assigned .3 Constraints .4 Assumptions 5.2 Scope Planning .1 Inputs .1 Product description .2 Project charter .3 Constraints .4 Assumptions .2 Tools and Techniques .1 Product analysis .2 Benefit/cost analysis .3 Alternatives identification .4 Expert judgment .3 Outputs .1 Scope statement .2 Supporting detail .3 Scope management plan 5.3 Scope Definition .1 Inputs .1 Scope statement .2 Constraints .3 Assumptions .4 Other planning outputs .5 Historical information .2 Tools and Techniques .1 Work breakdown structure templates .2 Decomposition .3 Outputs .1 W...
View Full Document

This document was uploaded on 09/27/2013.

Ask a homework question - tutors are online