Change Management
Change Management
• Controls the lifecycle of all changes Any change that does not alter the specification of a Configuration Item
• Responsible for formal assessment of a new or changed IT service (CI)
• Ensure that risks have been managed
Testing of an application, service or development project that will be
• Helps determine whether to authorize the change.
introduced as a part of normal change
• Enables beneficial changes to be made with minimum disruption to IT
**Some standard changes are not documented in the change
services.
management process; but instead are documented in incident
management process using a ticket submitted to the Service Desk.
Change Request Requirements
**However, a normal or emergency change may be triggered by a ticket in
• Impact statement/assessment the incident management process
• Implementation Plan **Therefore, it is not a standard change just because it started as a ticket
• Tasks or milestones needed to implement change within the incident management process… you must evaluate each
change or trigger individually
• Back out plan
• Anticipated downtime start and end times Note: This is not an all-inclusive list
(*) These items aren’t required for every change. However, if you are other documentation as relevant.
unsure if it is required for your change request please check with the • Entry into the event schedule by the Change Manager.
Change Manager.
Characteristics of a Standard Recurring Change
Characteristics of a Standard Change Reoccurs on a standard timeframe (weekly, bi-weekly, monthly, etc...)
Low in risk, impact and visibility Has same characteristics as a Standard Change but requires approval by
The tasks are well known, documented and proven Report completed occurrences to CM/CAB
RFC Submitted into SDP The tasks are well known, documented and proven
Pre-authorized change - CAB approval not required There is a defined Roll-Back plan
Any change that does not alter the specification of a Configuration Item Requires immediate attention
(CI) Usually in response to break/fix issue. They should never occur because
Testing of an application, service or development project that will be of poor planning.
introduced as a part of normal change
Restoring service, preventing an outage or repairing an error that is
severely impacting business
**It is possible for a recurring normal change that has been implemented
Testing reduced or forgone
successfully a couple of times to become a standard recurring change for
ECAB notified verbally or via email
future deployments.
RFC submitted w/in 1 business day of implementation or fix
Note: This is not an all-inclusive list
ECAB approves
Standard Recurring Change Requirements The percentage of Emergency changes occurring in the environment
should be very low.
• Notification of the implemented change to the Change Manager by the
start of the weekly CAB meeting.
• A change request and/or incident report if determined that it should have Examples of an Emergency Change
been implemented as a Normal Change including communications and A location is without a service
other documentation as relevant.
There is a severe degradation of service needing immediate action
• Entry into the event schedule by the Change Manager.
A system/application/component failure causing a negative impact on
business operations
Types of Changes
An enterprise application is unavailable
Standard
A response to a natural disaster
Standard Recurring
A response to an emergency business need
Emergency
A security breach requiring a patch to an enterprise server, enterprise
Normal
application or a large number of workstations
If a change is implemented outside one of these processes, it is an
Hardware malfunction has required a SQL database to be restored to
unauthorized change.
another server
• Submission of a Change Request within one business day after the Hardware failure to be fixed by a vendor
issue has been resolved
Note: This is not an all-inclusive list
• Post implementation review of the Emergency Change at the next CAB
meeting
Normal Change Requirements
• May require submission of an incident report to the Change Manager
and/or Security Administrator See section: Change Request Requirements
• May require engagement of an incident response plan if the change • Also requires approval by the CAB
request is the result of a hacker
• Communications may be needed Characteristics of an Unauthorized Change
Change that results in business interruption during regular business hours If you need additional information or need in-depth information, read the
Changes in any system that affects disaster recovery or business "ITI Change Management Process" document or go through the Change
continuity Management Process training material.
Install or relocate a printer that is high impact for a mission critical function