Change Control Process ITPD ISSUE MANAGEMENT PROCESS SEPTEMBER 5, 2008 March 10, 2015

Review of Project Control Processes Agenda Review of Project Control Processes Change Control

Change Control The process of reviewing and authorizing changes to the scope, schedule, or budget of the project, in reaction to a request which would alter the previously agreed upon Statement of Work or Project Charter. Guiding principle: in order to ensure a successful project launch, any significant alteration of previously agreed upon scope, schedule, or budget will be made only in exceptional circumstances and must be approved before any work may begin. Requests for Change are begun by the Project Team filling out a Change Request Form Those forms will be reviewed by the functional/technical leads and the Project Managers and then go for approval. Approvals begin with the PM Team, then can be escalated to Project Sponsors -> Exec Committee, if there is need. Links: Strategy doc

Change Control

Change Control - Process Steps Ref ID Process Step Description Input/Output Time Horizon Owner 1 Submit the Change Request Form Submit the Change Request form with any supporting documentation. Input: Identified change need. Output: Submitted CR form Any time Project Team 2 Log the Change Request Once the form has been submitted, it should be immediately logged in the change request log for tracking. Input: Submitted CR form Output: Logged CR Project Team (Coordinator) 3 Review Change Request The Project Manager will review the Change Request and go through two decision points. If the Change Request requires rework, then go to step 4. If not, then review CR and determine if further escalation is needed for approval. Input: Logged CR Output: Reviewed CR Project Manager 4 Rework Change Request Project Team should update the CR with any needed or supporting information that the Project Manager has implied was missing. Input: Reviewed CR Output: Resubmitted CR 5 PM approves/denies CR If Project Manager has determined that no additional escalation is required, then he/she approves or denies the request. Input: Reviewed CR Output: Decision on CR 6 Project sponsors approve/deny CR If Project Manager has determined that project sponsor approval is required, then project sponsors approve/deny the CR request Project Sponsors 7 Executive sponsors approve/deny CR If Project Manager and/or Project Sponsors have determined that executive sponsor approval is required, then executive sponsors approve/deny the CR request Executive Sponsors

Change Control - Process Steps Ref ID Process Step Description Input/Output Time Horizon Owner 8 Update Project Controls After the request has been approved/denied, then the Project Manager/Coordinator needs to update the Change Request log and any other appropriate project controls (plan, etc.) Input: Decision on CR Output: Updated Project Controls Any time Project Manager (Coordinator) 9 Communicate Decision to the Team After controls have been updated, inform the project team and other interested parties of the decision. Input: Decision on CR, Updated Project Controls Output: Communication message

Q&A 12/4/2018

For additional information on this process, please contact… Contact Information For additional information on this process, please contact… Contact Name Email Phone