Issues modern configuration management must address

"Survival of the fittest" means that only those who adapt best to a changing environment survive. In the software industry, requirements, technology, platforms and markets change very fast. Lehman's law of continuing change says that a system in use must keep changing or it becomes less and less useful. Software and companies that can change quickly without losing quality survive; those that cannot become obsolete.

Software configuration management (SCM) is the discipline that makes this possible. It identifies, controls, tracks and audits changes to software throughout its life. The "fittest" organizations are those whose SCM handles the following modern issues well.

Issues modern SCM must address

1. Version control at scale

   • Large systems have thousands of files and many versions, variants and releases at the same time.
   • SCM must store every version efficiently and retrieve any of them quickly.

2. Change control under rapid change

   • Agile methods and continuous delivery release software weekly or even daily.
   • Change requests must be evaluated, approved and tracked quickly, without slowing the team.

3. Parallel and distributed development

   • Teams in different countries work on the same code at the same time.
   • Branching, merging and conflict resolution must be reliable (distributed tools such as Git).

4. Dependency tracking and component reuse

   • Modern systems use many open-source libraries and third-party components with their own versions.
   • SCM must track which versions are used, manage updates, and handle security patches.

5. Build and release management

   • Systems must be built automatically and repeatably (continuous integration) and released to many platforms (web, Android, iOS).
   • SCM must record exactly which component versions form each release so it can be rebuilt.

6. Requirements tracing and impact analysis

   • Each change must be traced to the requirements, design, code and tests it affects, so its impact can be estimated before it is approved.

7. Configuration auditing and status reporting

   • Audits confirm that approved changes were made correctly; status reports tell everyone what changed, who changed it, when and why.
   • These are needed for quality assurance and for legal and regulatory compliance.

8. Content and people issues (web and cloud systems)

   • Web applications change content often and many people (developers, designers, content authors) change them.
   • SCM must control who may change what, and scale from small sites to very large systems.

9. Infrastructure and environment configuration

   • Server settings, databases and deployment scripts must also be versioned ("infrastructure as code") so environments can be re-created exactly.

Linking the two ideas

Example: a mobile wallet company must add a new payment method demanded by the market within two weeks while supporting old app versions. With good SCM it branches, implements, tests and releases quickly and safely; a competitor without SCM struggles with broken builds and lost changes and loses customers. In this sense, SCM is a key factor that decides which software products and companies are "fit" to survive.