Configuration Management Plan
Plans artifact · ← Artifact catalog
What it is
Notes on how versions of the plan itself are tracked and kept from getting confused.
Why it matters
Without it, nobody can say with confidence which version of the plan is the current one.
What it looks like here
Enforced structurally by baseline versioning rather than written as a document: each approved baseline carries its own version number.
Made by
No process in the catalog produces this artifact.
Used by
This product does not track this artifact against a real project's data — enforced structurally — read the baseline versions.
Reached from a project's own process map, this page also shows what that project's own data says about this artifact.