Section: Volume E

Section: Volume D
Explanation:
7.3.3.1 Cost Baseline
The cost baseline is the approved version of the time-phased project budget, excluding any management reserves, which can only be changed through formal change control procedures and is used as a basis for comparison to actual results. It is developed as a summation of the approved budgets for the different schedule activities.
Process: 7.3 Determine Budget
Definition: The process of aggregating the estimated costs of individual activities or work packages to establish an authorized cost baseline.
Key Benefit: The key benefit of this process is that it determines the cost baseline against which project performance can be monitored and controlled.
Inputs
1. Cost management plan
2. Scope baseline
3. Activity cost estimates
4. Basis of estimates
5. Project schedule
6. Resource calendars
7. Risk register
8. Agreements
9. Organizational process assets
Tools & Techniques
1. Cost aggregation
2. Reserve analysis
3. Expert judgment
4. Historical relationships
5. Funding limit reconciliation
Outputs
1. Cost baseline
2. Project funding requirements
3. Project documents updates

Section: Volume B
Explanation:
Configuration control is focused on the specification of both the deliverables and the processes; while change control is focused on identifying, documenting, and approving or rejecting changes to the project documents, deliverables, or baselines.
Some of the configuration management activities included in the Perform Integrated Change Control process are as follows:
Configuration identification. Identification and selection of a configuration item to provide the basis for

which the product configuration is defined and verified, products and documents are labeled, changes are managed, and accountability is maintained.
Configuration status accounting. Information is recorded and reported as to when appropriate data about

the configuration item should be provided. This information includes a listing of approved configuration identification, status of proposed changes to the configuration, and the implementation status of approved changes.
Configuration verification and audit. Configuration verification and configuration audits ensure the

composition of a project's configuration items is correct and that corresponding changes are registered, assessed, approved, tracked, and correctly implemented. This ensures the functional requirements defined in the configuration documentation have been met.

Section: Volume E
Explanation/Reference: https://www.projectmanager.com/blog/project-quality-management-quick-guide