Configuration Management
Official Definition:
The recording and updating of information about a project’s Deliverables, such as version number, storage location, and who has access.
Layman’s Definition:
Configuration Management keeps track of all the project’s stuff – what version it’s at, where it’s saved, and who can edit it. It’s like a filing system that helps avoid confusion.
Examples:
• Construction: Drawing versions updated and numbered as design changes are approved.
• Publishing: Managing multiple drafts of a policy document for stakeholder review.
• Software: Tracking code versions as features are tested and released.
When to Use:
Whenever Deliverables are being developed and changed during the project. Especially important during change requests.
What It Might Look Like in Practice:
• Each Deliverable is given a unique ID or version number.
• All versions stored in a shared repository.
• Log of who made changes, when, and why.
• Aligned with the Change Control process.