Change Report

Project Name: <<Enter Project Name >>

Client Name: <<Enter Client Name >>

Document Revision History

Docume
Change nt Approv
Request# Version al Date Modified By Section, Page(s) and Text Revised Approved By

Note: Template Revision History can be found in Hidden Text.

<<Text within Arrow Brackets (<< >>) are Instructions. Please delete the same while using the
Template>>

Table of Contents
1.Purpose................................................................................................................................... 2
Change request ......................................................................................................................... 2
Change Evaluation.................................................................................................................. 3
Change Request Acceptance Criteria...................................................................................... 3
Deliverables............................................................................................................................ 4
Estimate Change.................................................................................................................... 4
Schedule................................................................................................................................. 4
Risks....................................................................................................................................... 4
Assumptions........................................................................................................................... 4
Constraints............................................................................................................................. 4
Change Request Deployment Environment............................................................................. 5
Change Request execution......................................................................................................... 5
Requirements......................................................................................................................... 5
Design ................................................................................................................................... 5
Build ,Release, Deploy Change............................................................................................... 6
Verification and Validation...................................................................................................... 6
Approval................................................................................................................................. 6

<<Instruction: If any of the sections output is maintained externally provide a link to the file>>

Change Report 1
1. PURPOSE
The Application Change Report will be prepared for every Change Request received. This report, will be base lined, and
will undergo a version change whenever the scope of the original change request changes.

CHANGE REQUEST
<<This section is used to update the understanding of the CR with the client, prior to proceeding with Analysis>>

Change Request ID Priority:

Requested By: Request Date:

Organization: Contact Details:

Change Description

Reason for the

Change Request

Acceptance Criteria

Change Status Accepted

Rejected

Deferred

Approved By (CCB) Approved Date

Approved By Approved Date

(Client)

Change Report 2
Change Evaluation
<< Mention here the initial estimates arrived for the Change Request for submitting to CCB (include review and rework
activities)>>

Initial Estimation Size Measure

(Size)

Initial Estimation
(Effort in Person
Days)

Change Request Acceptance Criteria

<<Answer the following questions with respect to the change request before proceeding with the analysis. Correspond
and communicate with the client to update either the change request or this document with the results. Ideally, the
project team should aim to answer all the following questions and then the assumptions, constraints and risks should be
documented clearly. >>

1. Is the change request clearly and properly stated?

2. Are the requirements straightforward and understandable?

3. Do we have all the information needed to proceed with change request development?

4. Are the requirements stated in the CR consistent with each other?

5. Are the requirements stated such that it does not conflict with each other?

6. Are the requirements well structured (uniquely identified) within the change request?

7. Is the change request appropriate for implementation?

8. Are the requirements testable?

9. Are the requirements in sufficient detail?

Change Report 3
Deliverables
<<List all deliverables if any for the change. Obtain approval for the change. >>

ID Deliverable Name Date

Estimate Change
<<Record the detailed estimates in this section. >>

Schedule
ID Schedule Activity Planned Planned Planned Effort Actual Effort Completio
Start Date Finish Date (Hrs) (Hrs) n Date

1
2
3
4
5
6
7
8

Risks
<<Identify the risks involved during various phases of the development lifecycle. If maintained externally provide a link to
the file>>

Assumptions
<<Identify the list of assumptions based on which the estimates, schedules, design were planned. If maintained externally
provide a link to the file >>

Constraints
<<Identify the list of constraints that might impact the achievement of the project objectives>>

Change Report 4
Change Request Deployment Environment
<<Mention the deployment environment of the change, if applicable>>

CHANGE REQUEST EXECUTION

<<Document the results of the impact analysis and the corresponding estimates in this section. Clearly record the change
as Addition, Modification or Deletion and the version numbers of the items that are impacted>>

Requirements
<<List the requirements of the change for the following as applicable:

Phases

Team

Services

Database components

Organization

Application Systems

Infrastructure Systems

Interfaces

Documents

Service Continuity

Others

Design
<<Describe the design changes change for the following as applicable:

Phases

Team

Services

Database components

Organization

Change Report 5
Application Systems

Infrastructure Systems

Interfaces

Documents

Service Continuity

Others

Build ,Release, Deploy Change

<<Describe the changes performed in the various categories of the impacted items in this section or provide a link to the
documents that contained the changes here. Describe the release and deployment plan and other activities applicable for
the deployment phase.>>

Verification and Validation

<<Record the results of reviews and tests conducted on the changes that have been executed in this section.
List the criteria used for verification and validation.>>

Approval
<<Update the approval details like Approved By and Approved Date, obtained from the Client for Requirement analysis>>

Change Report 6