Examples of Rule Usage

The following examples show how two development teams apply CM rules for item and request types to meet their needs.

Example: A Highly Controlled and Visible Project

Team A is working on a highly controlled and visible project that requires a high level of control and visibility. From the start of the project, the team needs to use CM rules to ensure that no new revision is created unless it is related to a request and approved.

For item types, the team sets these rules:

For request types, the team:

Example: Prototype Project

Team B, a small group of designers, must produce a prototype of a system in a short amount of time. The goal is to demonstrate capability and win a contract. After winning the contract, the team will expand to a larger development group, and will need to impose more product controls to ensure consistent and repeatable overall functionality.

During the initial stages of the prototype project, the team disables CM rules for items and request types. This allows revisions to be freely created and actioned.

Just before delivery, the team enables CM rules to ensure that items in the release baseline cannot be further developed without request authorization.

For item types, the team sets these rules:

NOTE  Any item revisions that have already progressed beyond the state specified in the Action rule can still be actioned without the need for a request. The team must manage these items outside the scope of the rules specifications.

For request types, the team:

Following the delivery of the prototype, the team imposes further controls to prevent any unauthorized changes being made.