Continuous Delivery (CD) is a core practice within DevOps, which VeriSM™ incorporates as a progressive management approach. The primary contribution of CD to change control is the acceleration of change deployment. This is achieved by creating an automated pipeline for building, testing, and releasing software. By automating these stages, the process becomes faster, more reliable, and repeatable. This allows for frequent, small, and low-risk changes to be deployed rapidly, streamlining the traditional change control process by pre-approving standard changes that pass through the automated, quality-assured pipeline.

A. It imposes more rigorous and lengthy change control procedures.

This is incorrect. Continuous Delivery aims to make change processes faster and more efficient through automation, not more lengthy or manually rigorous.

B. It doesn't impact change control processes.

This is incorrect. Continuous Delivery fundamentally transforms change control from a manual, gate-based process to a highly automated, flow-based system.

D. It leads to a reduction in the frequency of change.

This is incorrect. A key goal and outcome of Continuous Delivery is to enable a higher frequency of smaller, incremental changes, reducing the risk of each deployment.

1. VeriSM™: A service management approach for the digital age. International Foundation for Digital Competences, 2017.

Section 4.4.2, Progressive practices (DevOps), Page 81: "DevOps is a cultural and professional movement that stresses communication, collaboration and integration between software developers and IT operations professionals... It supports the automation of the process of software delivery and infrastructure changes." This directly links the practice to automation and accelerating delivery, which is the essence of option C. The goal is described as "releasing more reliable applications faster and more frequently," which contradicts option D.

2. VeriSM™: Unwrapped and Applied. Van Haren Publishing, 2018.

Chapter 5, Section 5.2, DevOps, Page 102: "The goal of DevOps is to shorten the development lifecycle and provide continuous delivery with high software quality." This supports the concept of acceleration in option C.

Chapter 5, Section 5.2, DevOps, Page 104: Discusses how change management adapts in a DevOps environment: "In a DevOps environment, many changes will be classified as ‘standard changes’ and pre-approved. The change is then managed through the automated testing and release process." This explicitly describes how automation streamlines and accelerates the change process.