Develop Project Management Plan: Outputs

• Controlling and updating the scope, cost, budget, schedule and quality requirements based upon approved changes, by coordinating changes across the entire project. For example, a proposed schedule change will often affect cost, risk, quality, and staffing. • Documenting the complete impact of requested changes. • Validating defect repair. 4 • Controlling project quality to standards based on quality reports. Proposed changes can require new or revised cost estimates, schedule activity sequences, schedule dates, resource requirements, and analysis of risk response alternatives. These changes can require adjustments to the project management plan, project scope statement, or other project deliverables. The configuration management system with change control provides a standardized, effective, and efficient process to centrally manage changes within a project. Configuration management with change control includes identifying, documenting, and controlling changes to the baseline. The applied level of change control is dependent upon the application area, complexity of the specific project, contract requirements, and the context and environment in which the project is performed. Project-wide application of the configuration management system, including change control processes, accomplishes three main objectives: • Establishes an evolutionary method to consistently identify and request changes to established baselines, and to assess the value and effectiveness of those changes • Provides opportunities to continuously validate and improve the project by considering the impact of each change • Provides the mechanism for the project management team to consistently communicate all changes to the stakeholders. Some of the configuration management activities included in the integrated change control process are: • Configuration Identification. Providing the basis from which the configuration of products is defined and verified, products and documents are labeled, changes are managed, and accountability is maintained. • Configuration Status Accounting. Capturing, storing, and accessing configuration information needed to manage products and product information effectively. • Configuration Verification and Auditing. Establishing that the performance and functional requirements defined in the configuration documentation have been met. A Guide to the Project Management Body of Knowledge PMBOK ® Guide Third Edition 2004 Project Management Institute, Four Campus Boulevard, Newtown Square, PA 19073-3299 USA 97