How do you define the scope and level of configuration identification for your project?

1 Identify the configuration items

The first step is to identify the configuration items (CIs) that you need to manage and control in your project. CIs are the components or elements of your project that have a defined function, interface, or requirement, and that can be changed independently. Examples of CIs are hardware, software, documents, data, test cases, or processes. You can use a configuration identification plan or a configuration item list to document the CIs, their attributes, and their relationships.

2 Establish the configuration baselines

The next step is to establish the configuration baselines that represent the approved and stable versions of your CIs at different stages of your project. Configuration baselines provide a reference point for measuring and verifying the performance, quality, and functionality of your CIs. They also serve as a basis for managing and controlling the changes and deviations from the original specifications. You can use a configuration baseline matrix or a configuration baseline record to document the baselines, their dates, and their contents.

3 Define the configuration documents

The third step is to define the configuration documents that provide the information and guidance for the configuration management activities in your project. Configuration documents include the configuration management plan, the configuration identification plan, the configuration change management plan, the configuration status accounting plan, and the configuration audit plan. You can use a configuration document register or a configuration document index to document the documents, their versions, and their locations.

4 Assign the configuration identifiers

The fourth step is to assign the configuration identifiers that uniquely and consistently label your CIs, baselines, and documents in your project. Configuration identifiers help you to distinguish between different versions, variations, and revisions of your project deliverables. They also help you to trace and link your CIs, baselines, and documents across the project lifecycle. You can use a configuration identifier scheme or a configuration identifier standard to document the identifiers, their formats, and their rules.

5 Determine the level of detail

The fifth step is to determine the level of detail that you need to capture and maintain for your CIs, baselines, and documents in your project. The level of detail depends on the complexity, size, and nature of your project, as well as the stakeholder expectations, requirements, and regulations. You can use a level of detail matrix or a level of detail checklist to document the level of detail, its criteria, and its rationale.

6 Review and update the scope and level

The final step is to review and update the scope and level of configuration identification for your project as it evolves and changes. You should conduct regular reviews and audits to ensure that your configuration identification process is effective, accurate, and consistent. You should also update your configuration identification plan, list, matrix, register, scheme, and standard to reflect the changes and modifications in your project. You can use a configuration identification review or a configuration identification audit to document the review and update activities, their results, and their actions.