A Guide to Project Management

Am sa s 533 outputs from scope definition 1 work

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: mance, such as which interim deliverables have been completed and which have not. Performance reports may also alert the project team to issues that may cause problems in the future. .3 Change requests. Change requests may occur in many forms--oral or written, direct or indirect, externally or internally initiated, and legally mandated or optional. Changes may require expanding the scope or may allow shrinking it. Most change requests are the result of: An external event (e.g., a change in a government regulation). An error or omission in defining the scope of the product (e.g., failure to include a required feature in the design of a telecommunications system). An error or omission in defining the scope of the project (e.g., using a BOM instead of a WBS). A value-adding change (e.g., an environmental remediation project is able to reduce costs by taking advantage of technology that was not available when the scope was originally defined). Implementing a contingency plan or workaround plan to respond to a risk, as described in Section .4 Scope management plan. The scope management plan is described in Section A Guide to the A Guide to the 5.5.2 Tools and Techniques for Scope Change Control .1 Scope change control system. A scope change control system defines the procedures by which the project scope may be changed. It includes the paperwork, tracking systems, and approval levels necessary for authorizing changes. The scope change control system should be integrated with the integrated change control described in Section 4.3 and, in particular, with any system or systems in place to control product scope. When the project is done under contract, the scope change control system must also comply with all relevant contractual provisions. .2 Performance measurement. Performance measurement techniques, described in Section 10.3.2, help to assess the magnitude of any variations that do occur. Determining what is causing the variance relative to the baseline and deciding if the variance requires corrective action are important parts of scope change control. .3 Additional planning. Few projects run exactly according to plan. Prospective scope changes may require modifications to the WBS or analysis of alternative approaches (see Sections and, respectively). Project Project Management Management Body of Body of KnowledgeE L KnowledgeE PL MP AM SA S 5.5.3 Outputs from Scope Change Control .1 Scope changes. A scope change is any modification to the agreed-upon project scope as defined by the approved WBS. Scope changes often require adjustments to cost, time, quality, or other project objectives. Project scope changes are fed back through the planning process, technical and planning documents are updated as needed, and stakeholders are notified as appropriate. 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...
View Full Document

This document was uploaded on 09/27/2013.

Ask a homework question - tutors are online