Configuration Management
- Configuration Management
- the management activity consisting of the cohesive collection of all
tasks that are primarily performed to manage an
endeavor’s
baselines of
configuration items
As illustrated in the preceding figure, configuration management is part of the following inheritance hierarchy:
- Type: Abstract
- Superclass: Management Activity
- Subclasses:
The typical responsibilities of Configuration Management are to:
- Ensure that stakeholders know the major components of the endeavor.
- Minimize project disruption due to uncontrolled changes to major components of the endeavor.
- Provide an audit trail on why, when, and by whom baselined work products are changed.
- Identify configuration items and baselines to enable the retrieval of specific versions of work products and
baselines.
- Control changes to configuration items and baselines to minimize endeavor disruption.
- Report the status of changes to configuration items and baselines to all relevant stakeholders.
- Audit baselines to ensure that they consist of the correct versions of the correct configuration items.
Configuration Management typically may begin when the following conditions hold:
Configuration Management is typically complete when the following conditions hold:
- The endeavor is completed.
- The associated configuration items have been retired.
Configuration Management typically involves the following teams performing the following tasks in an iterative,
incremental, parallel, and time-boxed manner:
Configuration Management is typically performed using the following environment(s) and associated tools:
Configuration Management typically results in the production of all or part of the following work products in the
configuration management work product set:
Configuration Management tasks are typically performed during the following phases:
Phase |
Relevant Tasks |
Business Strategy |
Configuration Management Planning,
Configuration Identification,
Version Control,
Configuration Control,
Configuration Status Reporting, and
Configuration Auditing |
Business Optimization |
Configuration Management Planning,
Configuration Identification,
Version Control,
Configuration Control,
Configuration Status Reporting, and
Configuration Auditing |
Initiation |
Configuration Management Planning,
Configuration Identification,
Version Control,
Configuration Control,
Configuration Status Reporting, and
Configuration Auditing |
Construction |
Configuration Management Planning,
Configuration Identification,
Version Control,
Configuration Control,
Configuration Status Reporting, and
Configuration Auditing |
Initial Production |
Configuration Management Planning,
Configuration Identification,
Version Control,
Configuration Control,
Configuration Status Reporting, and
Configuration Auditing |
Full-Scale Production |
Configuration Management Planning,
Configuration Identification,
Version Control,
Configuration Control,
Configuration Status Reporting, and
Configuration Auditing |
Delivery |
Configuration Management Planning,
Configuration Identification,
Version Control,
Configuration Control,
Configuration Status Reporting, and
Configuration Auditing |
Usage |
Configuration Management Planning,
Configuration Identification,
Version Control,
Configuration Control,
Configuration Status Reporting, and
Configuration Auditing |
Retirement |
Configuration Management Planning,
Configuration Identification,
Version Control,
Configuration Control,
Configuration Status Reporting, and
Configuration Auditing |
- This activity is documented using the typical configuration for large endeavors. It is intended to be
configured (i.e., instantiated, extended, and tailored) to meet the needs of specific endeavors.
- The preconditions of this activity should be the union of the preconditions of its constituent tasks.
- The completion criteria for this activity should be the union of the postconditions of its constituent tasks.