Scribd
Upload
4 views6 pages

Change Request Management

CR process

Uploaded by

ranjithak
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
4 views6 pages

Change Request Management

CR process

Uploaded by

ranjithak
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Change Request

Management
• What is CR:

• Objective of Change request is to ensure that change request are managed,


tracked and implemented
• Change request shall be initiated whenever there is a need to change a baseline
product.
• A product is required to undergo change either due to a new requirement (FC) or
due to a bug (UC).

Examples: Any change in effort, schedule


defects, scope, resource
Steps
CR
• CR Contents
To be filled by the Change Initiator:
• Initiator Name:
• Project Name:
• Product Name:
• Change Description:

 To be filled by the Project Leader


Classification:
• Class A
• Class B
• Class C
SCR Type:
• New Requirement
• Discontinuity
• Enhancement
11/22/2024 Restricted and Confidential © KPIT Technologies Li 4
mited
To be filled by the Configuration Manager:

• SCR Number:
All SCRs are identified by unique number.
• Impact Analysis Number [in case of Class A/Class B ]:
Impact Analysis number from the IAR form has to be provided here.
• Forwarded to CCB: o Yes o No
This indicates whether CCB is convened or not
• Date Submitted to CCB:
Date on which SCR is submitted to the CCB
• CCB Schedule:
Provide the CCB Schedule including venue and time.

11/22/2024 Restricted and Confidential © KPIT Technologies Li 5


mited

You might also like