Scribd
Upload
643 views3 pages

Change Request Template

This document provides a template for a change request with sections for background, objectives, business process overview, business requirements, glossary of terms, and approvals. It outlines the necessary information to request changes to a project, system, or application including requirements, impacts, and an approval workflow.

Uploaded by

Rick Oldman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
643 views3 pages

Change Request Template

This document provides a template for a change request with sections for background, objectives, business process overview, business requirements, glossary of terms, and approvals. It outlines the necessary information to request changes to a project, system, or application including requirements, impacts, and an approval workflow.

Uploaded by

Rick Oldman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
  • Document Identification: Introduces the change request document including project name, requester, and approval details.
  • Business Requirements: Details the business requirements, including change items, user authority grants, and mock workflow requirements.
  • Estimated Mandays: Provides an estimate of the required mandays for IT divisions involved in the project.

Change Request Document

Document Identification
Project Name
Requester Name
Division/Department/
Unit
System/Application
Initial Date

Attached Documents
Version Date Description

Document Version History


Version Date Document Changes

Background
(Provide a brief history of how the project came to be proposed and initiated, including existing conditions, business needs and business
issues/problems identified.)

Objectives & Expected Improvements


(Describe the overall goal for this development, benefit, expected improvement, high level descriptions of what the end result of this
development can do and also requirements for interaction with other systems)
Benefit: Compliance Financial Process Others:………………….

Business Process Overview


(Describe how the current process(es) work, including interactions between systems and various business units. Include visual process flow
diagrams to illustrate the process improvements. Use case documentation and activity/process flow diagrams can be used to create descriptions
of the proposed process.)

Page 1 of 3
Change Request Document
Business Requirements
(List the specific business requirements here. Categorize each items priority.)
The requirements in this document are prioritized as follows:
Value Rating Description
1 Critical This requirement is critical to the success of the project. The project will not be possible without this requirement.
2 High This requirement is high priority, but the project can be implemented at a bare minimum without this requirement.
3 Medium This requirement is somewhat important, as it provides some value but the project can proceed without it.
4 Low This is a low priority requirement, or a “nice to have” feature, if time and cost allow it.

1. Change Items
No Product Feature/ Current Proposed
Enhancement
o o

2. User Authority Grant


Menu User Group Scope
HOBIS Trx Code Specify user group or job position Specify whether that user is granted access for all branches or
just user's respective branch

3. UI Mock Workflow Requirements


Put expected UI workflow here. Use a mock or wireframe if this requirement is for new menu or new feature. Use screenshot of existing UI
if it is available.
This part is very important, so please make sure that this part is not empty. Please coordinate with IT Project Management or related IT
Divisions for discussions and/or technical advisory.

Glossary of Terms
(Identify and define any terms/acronyms that may be unfamiliar to readers and also terms/acronyms that may be familiar to readers but
potentially resulting misinterpretations.)

Approvals
By signing below approval sheet, approver declare that he/she approve and acknowledge the commencement of development based on
specifications contained on this document.
Approval only if applicable (i.e. if development will not involve IT2, then no need approval from IT2).
Name Job Title Signature Comment
Sign and put approval date Put comment here if necessary
here

Development Estimation

Page 2 of 3
Change Request Document
IT 1 Division IT 2 Division
Estimated Mandays:
Filled by related IT Development
Estimated Start Date:
Filled by related IT Development

Page 3 of 3

Change Request Document Document Identification Project Name Requester Name Division/Department/ Unit System/Application Init
Change Request Document Business Requirements (List the specific business requirements here. Categorize each items priority.)
Change Request Document IT 1 Division IT 2 Division Estimated Mandays: Filled by related IT Development Estimated Start Date:

You might also like