Platform Implementation Project-Technical Team
Change Control Process
GWMP
Platform Implementation ProjectTechnical Team
TABLE OF CONTENTS
INTRODUCTION....................................................................................................................................................................... 3
INTRODUCTION ............................................................................................................................................................................ 3
PURPOSE ..................................................................................................................................................................................... 3
AUDIENCE .................................................................................................................................................................................... 3
CHANGE CONTROL PROCESS........................................................................................................................................... 3
PROCESS STEPS ......................................................................................................................................................................... 3
PROCESS FLOW .......................................................................................................................................................................... 4
ROLES AND RESPONSIBILITIES ........................................................................................................................................ 4
USER............................................................................................................................................................................................ 4
APPROVER ................................................................................................................................................................................... 4
CHANGE CONTROL ADMINISTRATOR .......................................................................................................................................... 4
REPORTS .................................................................................................................................................................................. 4
CHANGE CONTROL LOG .............................................................................................................................................................. 4
2
INTRODUCTION
Introduction
A Change Control process defines the method by which changes to a project scope are
identified and either accepted or rejected. It also preserves completed work and prohibits
alterations of that work without documenting changes.
Purpose
An effective change control process should:
 Provide a mechanism for accepting changes that improve the product overall while
rejecting those that degrade it.
 Facilitate changes to work products during their initial formative development while
avoiding unnecessary overhead or formality.
 Provide revision control and backup safety for work products during their formative
development.
 Allow for formal acceptance (approval) of work products after their initial formative
development has been completed.
 Facilitate efficient changes to work products after their initial acceptance, recognizing
that the impact of a change to a work product is dramatically different after the work
product has been accepted.
 Allow all parties materially affected by proposed changes to accepted work products
to assess the resource, schedule, and/or product impact of the changes.
 Allow changes to accepted work products to be proposed and evaluated, schedule and
quality impact assessed, and approved or rejected into work products in a controlled
manner.
 Provide an historic trail of the development of work products, including all proposed
changes.
Audience
The audience for this Change Control Process doc is:
 Project Sponsor
 Project Manager
 Project Team Members
 Client Implementation Project Manager
 Change Control Board Members
CHANGE CONTROL PROCESS
Process Steps
The name in BOLD is the person performing the step.
1. USER.
The user enters a Change Request into the Change Control Log in the e-room.
The user then sends an e-mail to the list of Approvers.
2. APPROVER.
On a weekly basis the Change Control Board meets to review any new Change
Requests. After reviewing a Change Request and evaluating the impact, each of the
Approvers makes a decision about the Request. If all accept then the Request is
3
accepted; if all do not accept the Request is not rejected. If there is insufficient
information to make a decision the Log is updated to reflect “Need More Info”.
3. CHANGE CONTROL ADMINISTRATOR.
The Change Control Administrator updates the Change Request and notifies the User
of the decision.
4. USER.
The User executes accepted changes or provides additional information, as requested.
Process Flow
The Process Flow looks like this:
User ――► Approvers ――► Administrator ――► User
ROLES AND RESPONSIBILITIES
User
Responsibility: beginning and end of Change Control process. Raises Change Requests.
Provides Change Request details, as requested.
Approver
Responsibility: Member of the Change Control Board. Accepts or Rejects Change Requests.
Change Control Administrator
Responsibility: Member of the Change Control Board. Maintains Change Control Log.
REPORTS
Change Control Log
Where: located in the e-room at https://eroom.seic.com/eRoom/sei/GWMPIMPS.
4