Skip to main content

Change Categorization

🔄 Note: Since the publication of this post, ITIL has evolved significantly. In ITIL 4, Change Management is now referred to as Change Enablement, with an emphasis on enabling frequent, agile, and value-driven change. The types of change—Standard, Normal, and Emergency—still apply, but decision-making is more decentralized with the introduction of Change Authorities. While the concepts in this post remain useful, we recommend pairing it with updated ITIL 4 guidance for a complete view.
Rusty asked:
I was looking for terms used for categorizing the impact of a change. I remember in Version 2 of ITIL that changes were categorized as Major, Significant, Minor, and Standard. Is that no longer done? Or is the impact also defined as the priority—High, Medium, and Low?
Rusty,

I’m going to give you my answer in three parts. This information can also be found in Section 4.2 of your Service Transition Book.
 
In ITIL V3 changes are now categorized into three distinct types:
 
Standard Change: Change to a service or infrastructure for which the approach has been pre-authorized by Change management that has an accepted and established procedure to provide a specific change requirement. It has a defined trigger, documented tasks and budgetary approval. The risk is low and well understood.

Normal Change: Change to a service or infrastructure for which the risk must be assessed and must go through the Change Advisory Board (CAB). These are Changes that happen either only once or infrequently and the impact/risk to the current environment must be assessed.

Emergency Change: Change that must be introduced as soon as possible, usually in order to repair an error within the environment. There is substantial risk involved and must be approved by the Emergency Change Advisory Board (ECAB). There is a separate escalation procedure in order to reduce or eliminate the impact/unavailability currently affecting the environment.

When assessing impact/risk we usually use an impact/risk categorization matrix and from this determine the associated scrutiny the change will receive by the Change Authority.
  • High impact/High probability = Risk Category 1 (Emergency change)
  • High impact/Low probability = Risk Category 2 (Normal change)
  • Low impact/High probability = Risk Category 3 (Normal change)
  • Low impact/Low probability = Risk Category 4 (Standard Change)
 When determining priority we use the formula:

 Priority = Urgency + Impact 

We can use the following examples of priority: 
  • Immediate – life at risk, significant loss of revenue (corrective)
  • High – Severely affecting key users or large # of users (corrective or innovative)
  • Medium – No severe impact, but cannot wait until next change schedule or release (corrective, innovative or update)
  • Low- Change is justified and necessary, but can wait until next change schedule or release.  (any type)
So we look at the Priority, exam the risk and this helps us determine the type of change we will use.

Comments

Popular posts from this blog

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.”  Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...

What is the difference between Process Owner, Process Manager and Process Practitioner?

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See  ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...