0% found this document useful (0 votes)
37 views2 pages

Change Request

This document is a change request and impact analysis form used to propose and assess changes to a project. It collects details of the proposed change including priority level and description. It then evaluates the technical, schedule, and effort impacts on tasks like design, coding, testing, and milestones. Risks to configurable project items are also analyzed. Final approval is needed from both the project manager and customer before the change can be implemented and later verified upon completion with signatures.

Uploaded by

Dharm Pal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
37 views2 pages

Change Request

This document is a change request and impact analysis form used to propose and assess changes to a project. It collects details of the proposed change including priority level and description. It then evaluates the technical, schedule, and effort impacts on tasks like design, coding, testing, and milestones. Risks to configurable project items are also analyzed. Final approval is needed from both the project manager and customer before the change can be implemented and later verified upon completion with signatures.

Uploaded by

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

Change Request and Impact Analysis Form

Change Details

Priority (High / Low)

Problem
Change Description
Request Number Date Raised

Description of changes required


Project Name

Initiator’s Name

Analysis Section (To be filled by the project leader)

Impact Description: (Attach extra sheets if required)


Implementation Effort
Impact on Milestone
Impact on Final Acceptance Date

Rework on design and coding


Technical impact

Schedule impact
Dates ho wmuch delay
Design incl Coding & Testing (Specify
Analysis
DB Unit Testing type)
Effort Impact <> Man
<> Man Days <> Man Days <> Man Days
Days
Total Effort: < > Man Days
Risk Analysis
Configuration ID Name
Configurable items Impacted

Is client’s approval required? (Yes


/ No)

Approval Section

Recommendation of PM/BUH
Recommendation of the
Customer
E-mail approval reference
Verification Section (To be filled by the PM after completion of the change)

Remark
Closure date & Signature

You might also like