Skip to main content

Change Categorization

Rusty asked:
I was looking for terms used for categorizing the impact of a change, I remember in Version 2 of ITIL that changes where categorized as Major, Significant, Minor and Standard is that no longer done? Or is the Imapct also defines 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

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 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 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.               Note: Goods may not always be provided for every Service Offe

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

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the