Explanation/Reference:
Explanation:
4.3.3.3 Change Requests
A change request is a formal proposal to modify any document, deliverable, or baseline. An approved change request will replace the associated document, deliverable, or baseline and may result in an update to other parts of the project management plan. When issues are found while project work is being performed, change requests are submitted, which may modify project policies or procedures, project scope, project cost or budget, project schedule, or project quality. Other change requests cover the needed preventive or corrective actions to forestall negative impact later in the project. Requests for a change can be direct or indirect, externally or internally initiated, and can be optional or legally/contractually mandated, and may include:
Corrective action-An intentional activity that realigns the performance of the project work with the

project management plan;
Preventive action-An intentional activity that ensures the future performance of the project work is

aligned with the project management plan;
Defect repair-An intentional activity to modify a nonconforming product or product component;

Updates-Changes to formally controlled project documents, plans, etc., to reflect modified or additional

ideas or content.

Explanation/Reference:
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.projectengineer.net/project-procurement-management-according-to-the-pmbok/