HKSM

A configuration management plan explains how configuration items and baselines will be identified, versioned, controlled, and reported throughout the project. It defines roles, tools, procedures, and audits, and integrates with the overall change control process.

Definition

A configuration management plan explains how configuration items and baselines will be identified, versioned, controlled, and reported throughout the project. It defines roles, tools, procedures, and audits, and integrates with the overall change control process.

Key Points

• Part of the project management plan that scales to project size and complexity.
• Centers on configuration items such as deliverables, documents, requirements, models, or code, and how they become baselined.
• Clarifies who can propose, review, and approve changes, and how versions are labeled, stored, and released.
• Aligns with change control, requirements traceability, and quality management to prevent unauthorized changes.
• Includes status accounting and configuration audits to verify completeness and correctness of items and baselines.
• Works for predictive and adaptive lifecycles, from formal boards to lightweight repository workflows.

Purpose

• Maintain integrity and traceability of scope and deliverables.
• Ensure only authorized and reviewed changes are implemented.
• Reduce rework and defects caused by using the wrong versions.
• Enable clear accountability for configuration decisions and approvals.
• Support compliance, audits, and knowledge transfer across the team.

Typical Sections

• Scope and objectives of configuration management.
• Configuration item identification and baselines.
• Change control process and decision authorities.
• Status accounting and reporting practices.
• Configuration verification and audit methods.
• Roles and responsibilities, including any boards or approvers.
• Tools, repositories, and naming or versioning conventions.
• Interfaces with other processes such as requirements, quality, and release management.

How to Create

• Define which deliverables and artifacts are configuration items and when they become baselined.
• Choose tools and repositories for storing, versioning, and tracing items.
• Set naming and versioning rules, branch or variant strategies, and release labels.
• Document the change control workflow, including request, impact analysis, decision authority, and communication steps.
• Specify status accounting reports, metrics, and dashboards to track item states and changes.
• Plan configuration audits and verification points aligned with milestones or increments.
• Assign roles and responsibilities, including requesters, reviewers, approvers, and administrators.
• Tailor rigor to the lifecycle and risk profile, and obtain stakeholder agreement.

How to Use

• Apply the identification rules and add new items to the registry when created.
• Baseline at agreed points, then route any proposed changes through the defined process.
• Use the specified repositories and conventions to store and retrieve the correct versions.
• Publish status reports so stakeholders can see pending requests, approvals, and releases.
• Run audits at planned times to confirm items match their specifications and records.
• Continuously align with change control and requirements traceability to prevent scope drift.

Maintenance Cadence

• Review the plan at kickoff, first iteration, and major phase gates.
• Reassess after significant scope, team, tool, or regulatory changes.
• In iterative projects, perform a quick check each sprint or monthly to keep practices current.
• Update naming, versioning, or approval rules when metrics show bottlenecks or quality issues.
• Log updates in the plan history and communicate changes to all contributors.

Example

• Configuration items: BRD v1.0, Design Spec v1.0, Product Increment Releases, Test Cases, Deployment Scripts.
• Baselines: Requirements baseline at Gate 1, Design baseline at Gate 2, Release baseline each iteration.
• Versioning: Semantic versioning MAJOR.MINOR.PATCH, release tags R-YYMMDD, document versions v1.0, v1.1.
• Change control: Requests logged in tracker, impact analysis within 2 business days, approvals by Change Control Board for major changes, Product Owner for minor changes.
• Status accounting: Weekly report of open requests, approved items, and released versions; dashboard in the tool.
• Audits: Pre-release configuration audit to confirm all approved changes are included and correctly labeled.

PMP Example Question

A project is ready to baseline its design documents and source code. The team wants to ensure only approved changes are released and that versions are traceable to requirements. Which artifact should define the process, roles, tools, and audits to achieve this?

1. Quality management plan.
2. Requirements management plan.
3. Configuration management plan.
4. Schedule management plan.

Correct Answer: C — Configuration management plan.

Explanation: The configuration management plan defines how configuration items are identified, baselined, versioned, changed, and audited. It integrates with change control and traceability to ensure controlled releases.