Scribd
Upload
2K views1 page

Change Management Process

The document outlines a change management process flow with the following key steps: 1. Changes are identified and logged before being assigned an initial priority and category. Emergency changes bypass some steps. 2. The change authorization board reviews and authorizes standard and significant changes. Minor changes are approved by managers. 3. Authorized changes are scheduled, built, tested, and implemented if tests are successful. Emergency changes are implemented after notification.

Uploaded by

HubVroon
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
2K views1 page

Change Management Process

The document outlines a change management process flow with the following key steps: 1. Changes are identified and logged before being assigned an initial priority and category. Emergency changes bypass some steps. 2. The change authorization board reviews and authorizes standard and significant changes. Minor changes are approved by managers. 3. Authorized changes are scheduled, built, tested, and implemented if tests are successful. Emergency changes are implemented after notification.

Uploaded by

HubVroon
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Change Management Process Flow

ITSM Academy 4/10/2006

MAJOR
Emergency
Circulates RFC
Change
to CAB
Assign initial priority
Identify
Change (emergency, high, Emergency
and Log
Management medium, low), urgency Change?
Change Determine SIGNIFICANT
and preliminary impact
Change Circulates RFC
Category to CAB
YES
Conduct
STANDARD impact
Emergency Circulates RFC analysis and
Change to CAB validate
category
(financial,
MINOR business,
Change technical
Manager or impact)
delegate
decides

Update and close


Obtain Change Change RFC and Release not
NO
Authorization Authorized? communicate accepted
decision

Release
YES Accepted

Schedule change Build and Test


and communicate Engage Release Change Test Implement Emergency
NO YES
to all affected Management? Successful? Change Change
parties (Standard/Minor)

Notify
YES Configuration
NO
Managers
Change
All major and YES and
Successful?
some significant communicate
change handled by to all affected
Release NO parties
Management
Enact
Backout
Plan Update RFC
YES
Log
Release
Management

Backout
Successful? Conduct Post-
Implementation
Review
NO

Incident
Configuration
Management
Management

You might also like