How does Change Control operate within CM?

How does Change Control operate within CM?

• A. It approves changes without evaluation to keep momentum.
• B. It handles requesting and implementing changes without baselines.
• C. It governs requesting, evaluating, approving, and implementing changes to baselined items.
• D. It forces all changes to be rejected unless senior management approves.

Answer: (C)

Change Control in Configuration Management ensures that any modification to configuration items goes through a formal, controlled lifecycle. It starts with a change request, followed by an evaluation of the impact on baselined items and related configurations, then formal approval (often by a Change Control Board) before the change is implemented. After implementation, the baselines are updated and the configuration management records reflect the new state, providing complete traceability of what changed, when, and by whom. This approach maintains the integrity of the configuration, prevents uncontrolled alterations, and keeps a clear record of changes. If a process approved changes without evaluation, it could introduce unforeseen risks. If changes were made without baselines, there would be no stable reference to manage against. If all changes were automatically rejected without appropriate authorization, legitimate needs would be blocked.

Change Control in Configuration Management ensures that any modification to configuration items goes through a formal, controlled lifecycle. It starts with a change request, followed by an evaluation of the impact on baselined items and related configurations, then formal approval (often by a Change Control Board) before the change is implemented. After implementation, the baselines are updated and the configuration management records reflect the new state, providing complete traceability of what changed, when, and by whom. This approach maintains the integrity of the configuration, prevents uncontrolled alterations, and keeps a clear record of changes.

If a process approved changes without evaluation, it could introduce unforeseen risks. If changes were made without baselines, there would be no stable reference to manage against. If all changes were automatically rejected without appropriate authorization, legitimate needs would be blocked.