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

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 policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…