According to the PMBOK Guide (Project Management Body of Knowledge), specifically within the Project Integration Management knowledge area, it is essential to distinguish between Change Control and Configuration Control:
* Configuration Control (Option B): This is the focused activity that provides a systematic way to manage and control the specifications of both the deliverables and the processes. It ensures that the product's attributes (functional and physical characteristics) are correctly identified, documented, and verified. It involves Configuration Identification (selecting and identifying configuration items), Configuration Status Accounting (recording and reporting), and Configuration Verification and Audit (ensuring the performance and functional requirements are met).
* Change Control (Option A): While closely related, change control is specifically focused on identifying, documenting, and approving or rejecting modifications to the project documents, deliverables, or baselines. It manages the alterations to the project, whereas configuration control manages the specifications and versions of the items themselves.
* Project Monitoring and Control (Option C): This is a broad process group consisting of those processes required to track, review, and regulate the progress and performance of the project. It is the " umbrella " under which change and configuration control reside, but it is not the specific " focus " of specification management.
* Issue Control (Option D): This refers to the management of " issues " -current conditions or situations that may have a negative impact on the project objectives. It is tracked via an Issue Log and does not deal with the technical specifications of deliverables or processes.
In the PMI framework, Configuration Management ensures that everyone is working with the correct version of the product specifications and that the " as-built " deliverable matches the " as-planned " requirements.