Explain like I'm five · SW Eng

What is Software Configuration Management (SCM)?

Configuration management, told as a story about a storage shelf that keeps every numbered edition of a manuscript safe.

edited on my PCbrought it in on a USBgot it by emailthe writer, editor, and proofreader each edited the same manuscript on their ownnobody knows which copy is the newest

The writer, editor, and proofreader each edited the same manuscript on their own.Nobody knows which copy is the newest.

the moment someone hits savewhoever saves last erases the person before them

Overwriting erases someone else's edits.Whoever saves last erases the person before them.

SCM = a storage shelf with numbered slotsevery version sits in its place, and you always know which is currentneed an old edition? just pull it from its numbered slot

Configuration management is a shelf with numbered slots.Need an old edition? Just pull it from its numbered slot.

Number every versionevery edition gets its own number
Keep a change logrecords who changed what, and when
Branch offexperiment on a copy, leave the original
Merge backonce the copy's change works, fold it into the original
BRANCH AND MERGEtest copytried a changeif the copy's edits work, they merge back into the shelf

You experiment with a branch, then merge it back.The original stays untouched while you try changes on a copy — then fold it back in if it works.

two of us edited the same linethe shelf won't decide which edit staysthe shelf doesn't resolve every conflict

The shelf doesn't resolve every conflict.If two edits collide, a person still has to reconcile them (a merge conflict). Backup and disaster recovery is a different story → the copy kept in the vault.

In one breath

Software Configuration Management (SCM) = a shelf that numbers and stores every edition, logs who changed what, and lets you branch off to experiment and merge back later.

Configuration management identifies changes to software artifacts (code, docs, configs), controls versions, and keeps the history traceable. It consists of four activities — identification, control, audit, and status accounting — carried out in practice with version control systems (VCS) like Git.

When grown-ups say it

Configuration Management
The shelf that keeps every edition safe. Made up of identification, control, audit, and status accounting.
Version Control System
The tool that actually runs the shelf. Git is the best-known example.
Baseline
The edition officially locked in. Every later change is compared against this point.
Branch
A branch where a test copy forks off. Lets you try changes without touching the original.
Merge
Folding the branch back in once it works. When merging extends into automatic deployment → using the shelf itself as the operating source of truth.
Rollback
Pulling an old edition back out, as-is. If a new edition has a problem, step back to the earlier slot → the rewind in the SRE field.
Change Control Board
The group that decides which changes get accepted. Important changes can't just be slotted in by anyone.
Configuration Audit
Checking that a shelved edition matches its approved documents and requirements. One of the things audit checks → the checker who watches the whole publishing run.
Next story
Caring for the Automatic Proofing Machine →
Want another term as a picture book? Request →