Configuration Management Team

Definition

Configuration Management Team

any team that manages the configuration of one or more related systems or applications and their associated work products

Classification

As illustrated in the preceding figure, the Configuration Management Team method component is part of the following inheritance hierarchy:

• Type: Concrete
• Superclass: Engineering Team
• Subclasses:
  • None

Responsibilities

The typical team-specific responsibilities of a Configuration Management Team are to:

• Identify the configuration items.
• Control changes to configuration items.
• Audit baselines.

A configuration management team typically inherits the general team responsibilities from the team method component.

Roles

A Configuration Management Team typically consists of persons playing the following roles:

• Configuration Manager, who:
  • Leads the team.
  • Plans the configuration management activity.
  • Performs configuration management tasks.
• Technical Writer, who produces and maintains the configuration management plan.

Tasks

A Configuration Management Team typically performs the following team-specific tasks in an iterative, incremental, parallel, and time-boxed manner:

• Configuration Management:
  • Configuration Management Planning
  • Configuration Identification
  • Configuration Control
  • Configuration Auditing
  • Configuration Status Reporting

A configuration management team typically inherits the common team tasks from the team method component.

Work Products

A Configuration Management Team typically produces all or part of the following work products:

• Documents:
  • Configuration Management Plan
  • Change Request Form
  • Configuration Identification Report
  • Configuration Status Report
  • Configuration Audit Report
• Concepts:
  • Baseline of configuration item (i.e., work products under configuration control)

Guidelines

• This team is critical to the success of the endeavor, even if it only consists of a single configuration manager.
• Change control is a collaborative effort of the configuration management team, the change control board, and all producers of documents and software work products, who usually store versions of work products in a configuration management tool.
• There is often a significant overlap of membership between the change control board and the configuration management team.