What is the value of Configuration Management (CM)?

What is the value of Configuration Management (CM)?

• A. Reduces loss of work and increases the ability to deliver the correct version of the solution to the customer.
• B. Increases rework by creating multiple versions.
• C. Eliminates the need for version control.
• D. Delays delivery by over-documenting changes.

Answer: (A)

Configuration Management provides discipline for identifying, controlling, and tracking changes to the product and its configuration items. This discipline keeps work from being lost or mismatched as changes happen and establishes baselines so you can hand the customer the exact version that meets requirements. By enforcing formal change control, maintaining traceability, and keeping accurate status and configuration records, CM reduces the risk of delivering the wrong version and minimizes rework caused by unmanaged changes. It also supports timely delivery because teams can coordinate changes, verify what changed, and reuse approved configurations instead of reconstructing them. The other options describe situations CM is designed to prevent—uncontrolled versions, unnecessary version control avoidance, or delays from over-documentation—where CM actually provides structure to avoid those outcomes.

Configuration Management provides discipline for identifying, controlling, and tracking changes to the product and its configuration items. This discipline keeps work from being lost or mismatched as changes happen and establishes baselines so you can hand the customer the exact version that meets requirements. By enforcing formal change control, maintaining traceability, and keeping accurate status and configuration records, CM reduces the risk of delivering the wrong version and minimizes rework caused by unmanaged changes. It also supports timely delivery because teams can coordinate changes, verify what changed, and reuse approved configurations instead of reconstructing them. The other options describe situations CM is designed to prevent—uncontrolled versions, unnecessary version control avoidance, or delays from over-documentation—where CM actually provides structure to avoid those outcomes.