A Guide to Project Management

2 supporting detail supporting detail is described in

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: the baseline can be documented. Configuration management. Configuration management is any documented procedure used to apply technical and administrative direction and surveillance to: Identify and document the functional and physical characteristics of an item or system. Control any changes to such characteristics. Record and report the change and its implementation status. Audit the items and system to verify conformance to requirements. In many application areas, configuration management is a subset of the change control system and is used to ensure that the description of the project's product is correct and complete. In other application areas, change control refers to any systematic effort to manage project change. Performance measurement. Performance measurement techniques such as EV (described in Section 10.3.2.4) help to assess whether variances from the plan require corrective action. Additional planning. Projects seldom run exactly according to plan. Prospective changes may require new or revised cost estimates, modified activity sequences, schedules, resource requirements, analysis of risk response alternatives, or other adjustments to the project plan. Project management information system. PMIS is described in Section 4.1.2.3. A Guide to the A Guide to the Project Project Management Management Body of Body of KnowledgeE L KnowledgeE PL MP AM SA S 4.3.3 Outputs from Integrated Change Control .1 Project plan updates. Project plan updates are any modification to the contents of the project plan or the supporting detail (described in Sections 4.1.3.1 and 4.1.3.2, respectively). Appropriate stakeholders must be notified as needed. .2 Corrective action. Corrective action is described in Section 4.2.1.5. .3 Lessons learned. The causes of variances, the reasoning behind the corrective action chosen, and other types of lessons learned should be documented so that they become part of the historical database for both this project and other projects of the performing organization. The database is also the basis for knowledge management. 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 49 ACROYMNS LIST Chapter 5 Project Scope Management A Guide to the A Guide to the Project Scope Management includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully (1). It is primarily concerned with defining and controlling what is or is not included in the project. Figure 5-1 provides an overview of the major project scope management processes: 5.1 Initiation--authorizing the project or phase. 5.2 Scope Planning--developing a written scope statement as the basis for future project decisions. 5.3 Scope Definition--subdividing the major project deliverables into smaller, more manageable components. 5.4 Sc...
View Full Document

This document was uploaded on 09/27/2013.

Ask a homework question - tutors are online