Create or release baselines for internal use and for delivery to the customer.

A baseline is represented by the assignment of an identifier to a configuration item or a collection of configuration items and associated entities at a distinct point in time. As a product or service evolves, multiple baselines can be used to control development and testing. (See the definition of “baseline” in the glossary.)

Hardware products as well as software and documentation should also be included in baselines for infrastructure related configurations (e.g., software, hardware) and in preparation for system tests that include interfacing hardware and software.

The acquirer reviews and approves the release of product baselines created by the supplier. The acquirer creates baselines for acquirer work products that describe the project, requirements, funding, schedule, and project performance measures and makes a commitment to manage the project to those baselines.

Example Work Products

1.    Baselines

2.    Description of baselines

Example Supplier Deliverables

1.    Product baselines

2.    Description of product baselines

Subpractices

1.    Obtain authorization from the CCB before creating or releasing baselines of configuration items.

2.    Create or release baselines only from configuration items in the configuration management system.

3.    Document the set of configuration items that are contained in a baseline.

4.    Make the current set of baselines readily available.