Change Control Board (CCB)

Definition

Change Control Board (CCB)

any team that determines when and if changes are to be implemented to baselined work products

Classification

As illustrated in the preceding figure, the Change Control Board method component is part of the following inheritance hierarchy:

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

Responsibilities

The typical team-specific responsibilities of a Change Control Board are to:

• Evaluate the impact of proposed changes to configuration items (possibly delegated to development team).
• Authorize/reject proposed changes to configuration items.

A change control board typically inherits the general team responsibilities from the team method component.

Roles

A Change Control Board typically consists of persons playing the following roles:

• Configuration Manager, who leads the change control board.
• Project Manager, who authorizes or rejects change requests.
• Customer Representative, who authorizes or rejects change requests.
• Domain Expert, who analyzes change requests.
• Requirements Engineer, who analyzes change requests.
• System Architect, who analyzes change requests.

Tasks

A Change Control Board typically performs the following team-specific configuration management tasks in an iterative, incremental, parallel, and time-boxed manner:

• Configuration Control:
  • Analyze change requests.
  • Authorize/reject change requests.

A change control board typically inherits the common team tasks from the team method component.

Work Products

A Change Control Board typically produces the following work products:

• CCB Meeting Minutes
• Change Request Form

Guidelines

• There is often a significant overlap of membership between the change control board and the configuration management team.