Configuration Management is… #Baselines!
Let’s talk about Baselines.
Imagine building a house without a blueprint. Each contractor works from their own notes, making changes as they see fit. The result? A structure riddled with inconsistencies, unexpected failures, and costly rework and delays. This is exactly what happens when organizations lack baselines in Configuration Management (CM).
What is a Baseline?
A baseline is a formally approved configuration snapshot at a specific point in time. It acts as a reference for defining changes and is used as a basis to order parts, manufacture and maintain products.
Without baselines, there’s no control over changes, no accountability for decisions, and no reliable way to verify product integrity.
What is the difference with a CM2 Baseline a.k.a. As Planned/As Released Baseline?
The CM2 Baseline is a rolling or moving baseline and is updated with every released dataset and includes visibility on the planned changes to the datasets and items in the baseline.
In Configuration Management, baselines serve three critical roles:
Control: They define what’s been agreed upon, preventing unauthorized changes.
Traceability: They provide a historical record of approved configurations.
Integrity: They enable verification and audit processes, ensuring compliance and consistency.
How does your organization manage baselines? Do you see them as a control mechanism or just a formality? Share your thoughts n LinkedIn.
Note: the CM is… series posts are not intended to limit the scope of Configuration Management, but to create awareness of the breadth of CM. Each of these elements is part of good Configuration Management Practice.