Change Management

Plan
VOICE RECOGNITION IMPROVEMENT PROJECT

Dr. Nguyen Duy Nghiem 11/18/21

Authorised by Nghiem D. Nguyen – nghiemnd@gmail.com i

Document Control

Document Information

Information
©

Document Id 180305_G5
Document Owner Nguyen Tan Tho
Issue Date November 1, 2021
Last Saved Date November 6, 2021
File Name QLPM.zip

Document History

Version Issue Date Changes

December 20,
[1.0] Update the interface of the Home page.
2021
December 20,
[1.1] Update the interface of the list buying advice and promotions.
2021
December 20,
[1.2] Add New Brand Page, New Products.
2021
December 20, Change the name "Experience instead, Go to the kitchen" to
[1.3]
2021 "Consultancy to buy, Delicious dishes every day".
December 20, Hide viewed product information when not needed with Clear
[1.4]
2021 Viewed History.
December 20,
[1.5] Add the list of industries
2021
December 20,
[1.6] Add product comparison category
2021

i
Authorised by Nghiem D. Nguyen – nghiemnd@gmail.com ii

Document Approvals

Role Name Signature © Date

Project Sponsor
November 1,
Dien May Xanh
2021
Project Review Group
Mr. Nguyen Duy November 4,
Nghiem 2021
Project Manager
November 4,
Bao Thanh Tran
2021
Quality Manager
November 4,
Ba Loc Dang
2021

Communications Manager November 4,

Thi Thuy Nguyen
2021
Project Office Manager November 4,
Tan Tho Nguyen
2021

ii
Authorised by Nghiem D. Nguyen – nghiemnd@gmail.com iii

Table of Contents

1 CHANGE PROCESS.........................................................................................................2
1.1 OVERVIEW.......................................................................................................................................2
1.2 SUBMIT CHANGE REQUEST................................................................................................................4

2 CHANGE DOCUMENTS..............................................................................................6
2.1 CHANGE REGISTER..........................................................................................................................6
2.2 Change Request Form....................................................................................................................6

iii
Authorised by Nghiem D. Nguyen – nghiemnd@gmail.com 1

Template Guide

What is a Change Management Process?

A Change Management Process is a method by which changes to the project (e.g. to the
scope, deliverables, timescales or resources) are formally defined, evaluated and approved
prior to implementation. The process entails completing a variety of control procedures to
ensure that, if implemented, the change will cause minimal impact to the objectives of the
project.

A Change Management Process is used to ensure that every change identified is formally:

 Communicated
 Documented
 Reviewed
 Approved
 Implemented. ©

When to use a Change Management Process

The Change Management Process is undertaken during the ‘Execution’ phase of the project
(i.e. the phase within which the deliverables are produced), once the project has been
formally defined and planned. In theory, any change to the project during the Execution
phase will need to be formally managed as part of the Change Management Process.
Without a formal Change Management Process in place, the objective of delivering a
solution within ‘time, cost and quality’ may be compromised.
©

The Change Management Process is terminated only when the Execution phase of the
project is completed (i.e. just prior to Project Closure).

How to use this template

This document provides a guide on the topics usually included in a Change Management
Process document. Sections may be added, removed or redefined at your leisure to meet
your particular business circumstance. Example tables, diagrams and charts have been
added (where suitable) to provide further guidance on how to complete each relevant
section.

1
Authorised by Nghiem D. Nguyen – nghiemnd@gmail.com 2

1 Change Process

1.1 Overview
Provide an overview of the Change Management Process. For example:

The Change Management Process is undertaken to ensure that each change introduced to
the project environment is appropriately defined, evaluated and approved prior to
implementation.

Change Management will be introduced to this project through the implementation of five key
processes:

 The submission and receipt of change requests

 The review and logging of change requests
 The determination of the feasibility of change requests
 The approval of change requests
 The implementation and closure of change requests. ©

The following diagram describes the processes and procedures to be undertaken to initiate,
implement and review the effects of changes within the project. Where applicable, Change
Roles have also been identified:

2
Authorised by Nghiem D. Nguyen – nghiemnd@gmail.com 3

3
Authorised by Nghiem D. Nguyen – nghiemnd@gmail.com 4

1.2 Submit Change Request

This process provides the ability for any member of the project team to submit a request for
a change to the project. The following procedures are completed:

Change Requester:

 Identifies a requirement for change to any aspect of the project (e.g. scope, deliverables,
timescales and organization) ©

 Completes a Change Request Form (CRF) and distributes the form to the Change
Manager. The CRF summarizes the change:

o Description
o Reasons
o Benefits
o Costs
o Impacts
o Approvals.

Description Reasons Benefits Costs Impacts Approvals

Easily find 500$

information
1.0 Update the Customers
in the
interface of the want High Accept
categories
Home page. change
at the top of
the page.
1.1 Update the Capture
interface of the Customers product
list buying want information Medium Accept
advice and change faster.
promotions.
Diversify the
1.2 Add New Customers
product,
Brand Page, want Medium Accept
convenient
New Products. change
for selection.
1.3 Change the Easily
name choose to
"Experience buy new
instead, Go to products
Customers
the kitchen" to and refer to
want Medium Accept
"Consultancy product
change
to buy, information
Delicious in new
dishes every pages.
day".
1.4 Hide Customers Hide viewed Medium Accept
viewed product want product
information change information
when not when not

4
Authorised by Nghiem D. Nguyen – nghiemnd@gmail.com 5

needed with
needed with
Clear
Clear Viewed
Viewed
History.
History.
Diversify the
Customers
1.5 Add the list types of
want Medium Accept
of industries. goods in the
change
system.
Easy to
choose,
1.6 Add
Customers consider
product
want comparing Low Accept
comparison
change products of
category.
different
brands.

Priority Describe
High Change should be given the highest priority
Medium Change needs to be prioritized
Low Change doesn't need to be prioritised

5
Authorised by Nghiem D. Nguyen – nghiemnd@gmail.com 6

2 Change Documents
List any other documentation used to monitor and/or control changes to the project.

2.1 Change Register

The ‘Change Register’ is the log / database where all requests for changes are registered
and tracked through to resolution.

2.2 Change Request Form

The ‘Change Request Form’ is used to identify and describe a proposed change to the
project.

CHANGE REQUEST
PROJECT NAME CHANGE REQUEST NUMBER
PROJECT MGR.
CHANGE REQUEST
DATE OF
REQUESTER NAME REQUEST
REQUESTER CONTACT PRIORITY
ITEM TO BE CHANGED
CHANGE DESCRIPTION
PREDICTED TIMELINE ESTIMATED COSTS

CHANGE EVALUATION
EVALUATOR NAME DATE OF EVAL
EXPECTED OUTCOME

WORK REQUIRED

AREA OF IMPACT IMPACT DESCRIPTION IMPACT LEVEL

SCOPE
SCHEDULE

6
Authorised by Nghiem D. Nguyen – nghiemnd@gmail.com 7

COST

QUALITY
CHANGE REVIEW / APPROVAL
REVIEWER NAME STATUS
DATE OF
REVIEWER SIGNATURE REVIEW

ADDITIONAL COMMENTS

CHANGE TRACKING

TRACKING AGENT LAST UPDATED

TRACKING AGENT VERSION
SIGNATURE NUMBER

ADDITIONAL COMMENTS