Scribd
Upload
424 views12 pages

Change Control Register

The document outlines a change management process for a project. It describes how change requests are submitted and assessed for impact on timelines, efforts, and costs. Change requests are discussed in weekly meetings and approved requests are implemented in iterations. For each iteration, the summary provides the estimated effort in person-hours for development and testing, timeline impact in days, and cost impact in USD. It also lists the change requests included in each iteration along with their submission dates.

Uploaded by

Sunil Benedict
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
424 views12 pages

Change Control Register

The document outlines a change management process for a project. It describes how change requests are submitted and assessed for impact on timelines, efforts, and costs. Change requests are discussed in weekly meetings and approved requests are implemented in iterations. For each iteration, the summary provides the estimated effort in person-hours for development and testing, timeline impact in days, and cost impact in USD. It also lists the change requests included in each iteration along with their submission dates.

Uploaded by

Sunil Benedict
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
  • Change Management Process: Describes the steps and procedures for managing change requests in a project, including assessments and sign-off processes.
  • Impact Assessment: Outlines the framework and factors considered in assessing the impact of project changes, including cost impacts.
  • Change Request Form: Provides the template and fields required for completing a change request form, focusing on impact and remarks.
  • Change Control Register: Contains a sample log for tracking change requests and their statuses throughout a project lifecycle.
  • Change Iteration Impact on Timeline: Details multiple change iterations and their effects on project timelines and resource allocations.

<Project Name>: Change Management Process

1 Change request is raised and submitted to India Project Team (Om, Swati) via email. Send copy to the Impact Assessment Group
2 High level assessment by India Project Team
3 Impact assessers to meet every Monday and Thursday to discuss and take decisions on the CRs. Attached register to be shared ah
4 Email sign-off on the accepted changes by the sign-off authority group. Associated coomerical and timeline related impact to be
5 Team will make appropraiate amendments in the vendor contract (If applicable).
6 Project plan is updated with new timeline, resources and efforts

Sign-off Authority Group


A
B
C
D
E If budget exceeds Contingency

Summary of

CR Block (Iteration) Timeline Impact (Days) Effort Impact (person-Hours)


4,14 18 144
18,19,22,25 9 70
26 15 120
27,28,29,30,31 16 128
Total 58 462
il. Send copy to the Impact Assessment Group

ns on the CRs. Attached register to be shared ahead of meeting.


coomerical and timeline related impact to be signed off as relevant.

Impact assessment group


A J
B O
C V
F L
K

Summary of Timeline, Effort & Cost Impact

Cost Impact (USD) Milestone Dates Impact


3780 None
1838 None
3150 None
4404 None
13171
meeting.
ff as relevant.

e, Effort & Cost Impact

Remarks
Project: Change Control Register
Corr. Client Estimated Effort for
CR No. Date of request Description of Change Nature of Module/functionality Status Exp Dev & Testing Actual date of Actual Effort for Dev+
CR No. Requester Comments by Impact Assessment Group Dev+ Testing
Request Impacted date Implementation Testing (person-hrs)
(person-hrs)
CR01 2 4-Jan-12 Change Approved
Remarks Recieval date

4-Jan-12
<Project Name>: Change Iteration Impact on Timeline
Timelines:

Timelines (days) 1 2 3 4
Development
CR Testing
Regression testing
Development
CR Testing
Regression testing

Efforts:

Total Man hours required: 144 hrs for development and testing.
1st Change Iteration Total Person days required = 18
Testing would involved
·         Test scenario and cases preparation for new functionality
·         Test execution for new functionality
·         Regression testing for existing functionality

For reference:

CR 4-Jan-12

CR 4-Jan-12

Timelines:

Timelines (days) 1 2 3 4
Development
CR18 Testing
Regression testing
Development
Testing
CR19 Regression testing
Development
Testing
CR22 Regression testing
Development
Testing
CR25 Regression testing

Efforts:

2nd Change Iteration


Total Man hours required: 70 hrs for development and testing.
2nd Change Iteration Total Person days required = 8.75
Testing would involved
·         Test scenario and cases preparation for new functionality
·         Test execution for new functionality
·         Regression testing for existing functionality

For reference:

CR 18-Jan-12

CR 18-Jan-12

CR 25-Jan-12

CR 25-Jan-12

Timelines:

Timelines (days) 1 2 3 4
Development
Testing
Regression testing

Efforts:

Total Man hours required: 120 hrs for development and testing.
3rd Change Iteration
Total Person days required = 15
Testing would involved
·         Test scenario and cases preparation for new functionality
·         Test execution for new functionality
·         Regression testing for existing functionality

For reference:

CR 14-Feb-12
5 6 7 8 9 10

for new functionality

5
for new functionality

5 6 7 8 9 10 11 12 13

for new functionality

You might also like