0% found this document useful (0 votes)
175 views6 pages

Configuration Management & Change Process Guide

The document describes the configuration management (CM) process and change management process. For CM, it involves: 1) Identifying configuration items, 2) Maintaining repositories, 3) Assigning a CM manager and change control board, 4) Logging and tracking changes, 5) Defining release baselines, 6) Implementing baselines and changes, and 7) Conducting audits. The outputs are updated project plans, CM plans, versioned work products, and audit reports. For change management, it involves: 1) Identifying change requests, 2) Evaluating changes, 3) Reviewing by the change control board, 4) Implementing changes, and 5) Validating and closing changes

Uploaded by

mtechewit
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
175 views6 pages

Configuration Management & Change Process Guide

The document describes the configuration management (CM) process and change management process. For CM, it involves: 1) Identifying configuration items, 2) Maintaining repositories, 3) Assigning a CM manager and change control board, 4) Logging and tracking changes, 5) Defining release baselines, 6) Implementing baselines and changes, and 7) Conducting audits. The outputs are updated project plans, CM plans, versioned work products, and audit reports. For change management, it involves: 1) Identifying change requests, 2) Evaluating changes, 3) Reviewing by the change control board, 4) Implementing changes, and 5) Validating and closing changes

Uploaded by

mtechewit
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd

<ADTL Logo>

By

Inputs Preparation of the engineering documents Configuration Item identification Implementation of the approved changes PM plan

Customer and Internal team (Across all phases)

Methods (Templates, Checklists, Guidelines/Work instructions) CM plan template CM audit checklist CR log template PM template Traceability Matrix Stakeholders involved Delivery Manager Project Manager Technical Lead Configuration Management(CM) in charge

Turtle Diagram Configuration Management (CM)


1. Identifying configuration items that will be subject to change control 2.Documenting repositories and processes for maintaining configuration items 3.Identifying and establishing a project configuration manager and change control board 4.Logging and tracking all potential project changes 5.Defining project release baselines 6.Implementing and communicating baselines and changes 7. Conduct configuration audits to to verify that a product has achieved consistency and accuracy of its product requirements, and product configuration information.Configuration audits will be conducted at the frequency defined in the PM plan.

Outputs

Metrics Effort Compliance check

Tailoring The templates can be modified , however the contents must same as defined in ADTL QMS The access rights and the Directory structure can be as per project

Rationale if customer provided If customer defined

To Updated Project plan Reviewed and approved CM plan Baselined Work products in version control tool Master list updated with the changes done CM audit report

Customer & To internal team

Lessons learned conducted

<ADTL Logo>

By

Inputs Requirement / Functionality change request Changes from reviews and testing

Customer and

Internal team

Defects reported by customer Baselined work products PM plan

Methods (Templates, Checklists, Guidelines/Work instructions) CM plan template Change request form CR log template Traceability Matrix

Stakeholders involved Delivery Manager Project Manager Technical Lead Configuration Management(CM) in charge Change control board (CCB)

Turtle Diagram Configuration Management (CM) CHANGE MANAGEMENT PROCESS


1. Change Identification - Requester observes a need for a change request (CR) or a problem with the current system. Submit the CR to the CCB.

Outputs
2.Change evaluation - The CR form is checked for validity, that is, for completeness and reasonability.The project lead, along with the CCB and project team, will do a thorough impact analysis on the change received. *Decision Analysis Resolution process can be used to arrive at the best solution to the CR. Attach the relevant DAR template. (IF Applicable) 3.The CCB reviews the change tasks along with the relevant documentation and indicates the level of approval in the form 4. Change Implementation - The change is implemented in the required workproducts, If the changes require additional modifications, a loop is followed till the changes are accepted. 5.Validate the change, close the CR and notify the requester

Metrics Effort Compliance check

Tailoring The templates can be modified , however the contents must same as defined in ADTL QMS

Rationale if customer provided

To

Updated Project plan Updated SRS, Design, Code files,Test documents(work products)

Customer &

To internal team

Impact analysis report Project progress report Risk Tracker updated as required. Updated CR log Lessons learned conducted

You might also like