CONFIGURATION MANAGEMENT

Maturity Level 2 – Support GroupCMMI V1.2

Process Owner – Ramya24st Dec. 2009 Thursday

QUALITY MANAGEMENT SYSTEMSQUALITY MANAGEMENT SYSTEMSPage Page 1616

The Process AreasThe Process Areas

• Organizational Training• Organizational Process Definition

+ IPPD• Organizational Process Focus

• Organizational Process Performance

• Supplier Agreement Management• Project Monitoring and Control

• Project Planning

• Risk Management• Integrated Project Management

+ IPPD

• Quantitative Project Management

• Requirements Management

• Validation• Verification

• Product Integration• Technical Solution

• Requirements Development

• Organizational Innovation & Deployment

• Configuration Management• Process & Product Quality Assurance

• Measurement & Analysis

• Decision Analysis & Resolution

• Causal Analysis & Resolution

Engineering Project Management Process Management Support

2

3

4

5

2

3

4

5

• A carelessly planned project takes three times longer to complete than expected; a carefully planned project takes only twice as long.

Whose requirement?

• This process is not CMMI requirement but it is OUR requirement.

Purpose of CM

• The purpose of Configuration Management (CM) is to establish and maintain the integrity of work products using configuration identification, configuration control, configuration status accounting, and configuration audits.CMMI V1.2 page 114

• Judgments may need to be made about whether the value of the results will be commensurate with the resources devoted to doing the work.

Configuration Management Plan

• Organizational level Plan• Project level Plan

Specific Goal and Practice Summary

• SG 1 Establish Baselines– SP 1.1 Identify Configuration Items– SP 1.2 Establish a Configuration Management System– SP 1.3 Create or Release Baselines

• SG 2 Track and Control Changes– SP 2.1 Track Change Requests– SP 2.2 Control Configuration Items

• SG 3 Establish Integrity– SP 3.1 Establish Configuration Management Records– SP 3.2 Perform Configuration Audits

• Configuration Items (Tier-1)• Version Control Documents (Tier-2) • Non-version Control Documents (Tier-3)

• SP 1.1

Identify Configuration Items

The work product shall be placed under configuration management if it satisfies any one of the following conditions.

1) Work products that may be used by two or more groups2) Work products that are expected to change over time either because of errors or change of requirements3) Work products that are dependent on each other in that a change in one mandates a change in the others4) Work products that are critical for the project

Criteria for Selection of Work Products to be placed Under Configuration Management

Typical examples of the work product to be placed under configuration management are as follows.

1) Process descriptions (Standard Operating Procedures, Work Processes etc.)2) Requirements (Contract Document, Input data etc.)3) Design (Calculations, Drawings, Specifications etc.)4) Interface descriptions

Establish Configuration Management System

• Organizational Level– Process Asset Library (PAL)– S&L Standard tool– PIP Portal– Knowmore– With Backup procedure

• Project Level– Project server drive on the network– PLADES server – CICO server– Hard copy storage system

• S P 1.2

Create or Release Baselines

• A baseline is a set of specifications or work products that has been formally reviewed and agreed on, that thereafter serves as the basis for further development or delivery, and that can be changed only through change control procedures.

• SP 1.3.

Track and Control Changes

• Configuration Control Board (CCB)– Organizational Level– Project Level

• To control the changes to the various configuration items, both projects and organizational related, proper authorization shall be sought from Configuration Control Board (CCB).

• SP 2.1 & SP 2.2

Establish Integrity

• Revision history of configuration items shall be maintained.• The updated Project Deliverable List shall be maintained.• The updated vendor document list and or the PDIS report indicating current

status of vendor documents shall be maintained.• The design change notice (DCN) log sheet shall be maintained.• The updated Process Asset Library (PAL) content list shall be maintained.• The updated software list shall be maintained in the Process Asset Library

(PAL)

• Audits

• SP 3.1 & SP 3.2

Generic Goal and Practices Summary

• GG 2 Institutionalize a Managed Process

– GP 2.1 Establish an Organizational Policy– GP 2.2 Plan the Process– GP 2.3 Provide Resources– GP 2.4 Assign Responsibility– GP 2.5 Train People– GP 2.6 Manage Configurations– GP 2.7 Identify and Involve Relevant Stakeholders– GP 2.8 Monitor and Control the Process– GP 2.9 Objectively Evaluate Adherence– GP 2.10 Review Status with Higher Level Management

• GG 3 Institutionalize a Defined Process

– GP 3.1 Establish a Defined Process– GP 3.2 Collect Improvement Information

• SOP 0404 DOCUMENT AND DATA CONTROL– Rev 0 15.06.2002– Pages : 2 no.– SOP Owner:

• SOP 0405 CONTROL OF EXTERNAL CODES AND STANDARDS– Rev 1 07.09.2009– Pages : 2 no.– SOP Owner:

• SOP 0408 FILING AND STORAGE OF PROJECT DOCUMENTS– Rev 0 15.06.2002– Pages : 6 no.– SOP Owner: