Key Principles of Software Configuration Management in Continuous Delivery 2.0

Based on Chapter 11 of Jo Liang's book Continuous Delivery 2.0 , the author explains why software configuration management (SCM) is the foundation of the "everything automation" principle that accelerates the continuous delivery verification loop.

Principle 1 – Everything Has a Version: All artifacts involved in production—source code, configuration files, test libraries, test data, scripts, etc.—should be stored in version‑controlled repositories. By categorising them into OS layer, standard software layer, and application layer, each change creates a new snapshot, ensuring traceability and reproducibility.

Principle 2 – Share a Single Trusted Source: The organization must manage all repositories (requirements, code, package) centrally so every team member works from the same baseline. Package repositories include temporary artifact stores, official release stores, and private external package servers, all of which need proper governance.

Principle 3 – Standardisation and Automation: SCM should be governed by clear standards such as branch strategies, naming conventions, tag policies, product‑feature naming, directory structures, etc. When everyone follows these standards, communication overhead drops and routine tasks can be automated, reducing manual errors.

The author stresses that standardisation does not mean rigidity; continuous improvement mechanisms must be in place, especially for large teams.

To assess whether a team has effective SCM, five basic questions are proposed (e.g., are source code and test code in version control? Are configuration and environment settings versioned? Are build and deployment scripts versioned? Are software packages versioned?). Two additional challenge questions test the ability to build the entire product from a single checkout and to enable any team member to trigger a full automated build.

By repeatedly reviewing these questions, teams can identify gaps and strengthen the SCM foundation, ultimately improving development efficiency in fast‑changing internet environments.