CHANGE LOG

PROJECT DETAILS
PROJECT No: MA-015-02
DATE:

FULL PROJECT NAME: Project Orion

PROJECT MANAGER: A Smith

PROJECT SPONSOR: F Dole

 CHANGE LOG
REASONS FOR THE
ID DATE REQUESTED BY CHANGE REQUEST DESCRIPTION CHANGE STATUS

1 Feb-21 P swift Change custom menu 238 to new status list. New status list introduced. APPROVED

Ability to save pages under

2 Jan-21 D James Save to favourites function. customer's account page. REJECTED

3 Dec-20 D James Additional action box widget. To show latest stock prices. PENDING

4 Dec-20 P swift Change color <h1> tags to dark green. To match customer scheme. PENDING

5 Jan-21 T Dent Add recall page for product W132 SCANNER Recall required urgent APPROVED

6 Jan-21 T Dent Change 'client' to 'customer' throughout site. To match new style guide. APPROVED
CHANGE LOG
PROGRESS OF PENDING AND APPROVED
CHANGES / REASON FOR REJECTION ACTIONS RELATED TO THE CHANGE NOTES

Tested and approved for go live. no further action. Added to go live plan task 148.

Rejected as just a nice to have consider for future phase. no further action. Added to draft phase 2 requirements.

D. James getting estimate of monthly cost

more information needed on pricing of api calls. based on 1 call per hour.

Approved pending confirmation of exact hexdecimal P Swift to get css and # from customer
code. marketing team. Task ID 138 on project schedule.

T Dent to change marketing and submit to

Page copy with marketing for appoval. web team. Task ID 138 on project schedule.

Completed, tested and approved for go live no further action. Added to go live plan task 149.
 DEFINITIONS
PROJECT MANAGER

The person with responsbility for managing and delivering the project. They will own this log, but may not be the person maintaining i

PROJECT NO.

The project number is assigned by the PMO (Project Management Office) once the project is approved for funding.

PROJECT SPONSOR

The person with ultimate accountablity for the project. They will hold the purse strings.

FULL PROJECT NAME

The name of the project, this should align with the name given on other project documents (rather than being a nickname).

CHANGE ID

Give each change a unique identifier or reference so that it can be easily traced.

CHANGE DATE

Enter the date of the change from the change request.

CHANGE REQUESTOR

Enter the name of the person or team who requested the change.

CHANGE REQUEST DESCRIPTION

Describe the change. This could be copied from the change request form.

REASON FOR THE CHANGE

Describe the reason for the change. For example to resolve and issue or change the scope of a deliverable.

STATUS

Select the status of the change. For example: pending, approved, rejected.
PROGRESS OF PENDING AND APPROVED CHANGES / REASON FOR REJECTION

Describe the progress of the change. For example, in design phase or in UAT.

ACTIONS RELATED TO THE CHANGE

Note down any further actions. For example, if the change request status is pending, what information is needed before it can progres

This template was provided by

https://www.stakeholdermap.com/
 HOW TO CHANGE THE MENU ITEMS IN STATUS FIELDS
Default settings
We have not set any drop down menus, as it is likely that most projects will have different priorities and categories.
How to create a drop down menu
Click on Data tab > Data Validation > Settings > List
In the Source field enter the menu items separated by a comma.
To change the menu items
To change the menu options or remove the dropdown select Data > Data Validation > Settings > List

ADDITIONAL FIELDS YOU MIGHT WANT TO ADD

Change Category
Team or person implementing the change
References or links to related documents e.g. updated WBS or project schedule.
Change impact in terms of budget or schedule.

This template was provided by

https://www.stakeholdermap.com/
CHANGE REQUEST TEMPLATE

CHANGE MANAGEMENT PLAN

CHANGE MANAGEMENT PROCESS

CHANGE MANAGEMENT RACI

CHANGE REQUEST MEANING AND DEFINITION