Skip to main content

Change Management People

“Those Change Management people make my life so difficult sometimes!”

I heard this from one of my students the other day. In this person’s organization they have made a common error. They have confused the process of Change Management with the Service Desk, Technical, Operations and Application Management functions. In other words the people who use the Change Management (and other processes) have become the same as the process itself. This is an often misconstrued and misinterpreted idea.

We must remember that ITIL makes a distinction between Functions (groups of people who use processes to complete similar types of work) and Processes (sets of activities used to complete various types of work). I like to remind my learners that Functions use Processes (or people do activities). Functions are not Processes and Processes are not Functions.

There may be groups of people or work teams who use a process as their main tool. As an example, the Release Implementation Team could use Release Management as their main set of activities. But, they may also use Change Management (and probably will) or Configuration Management or any other process to implement a Release.

This is also true of the Functions. The Service Desk does not only use Incident Management. They certainly will also use Request Fulfillment, Access Management, possibly Problem Management, Change Management and many others. The goal of the Service Desk is to use whatever processes and tools available to restore normal service operations as quickly as possible.

The people in the Functions wear many hats and fulfill many process roles. Generally they can only wear one hat at a time, but could have a number of hats in their wardrobe. They may do Incident Management activities for 30 minutes and then need to switch to Problem Management for an hour and then over to Availability Management for the afternoon. They are still the same person with the same title, but they have many roles and responsibilities.

When a person tries to do many roles simultaneously they often find it difficult to juggle. It generally works better that we each do one role at a time and we each follow one process at a time. When we complete a given set of process steps we go on to the next or another process. And then to the next.

Because we can wear many hats and use many processes as a set of tools or a “kit” to complete an action or produce an outcome or output it should not be thought of as only one group of people who do Change Management. The processes are spread across the functions. You might have a group of people dedicated to the support and care and feeding of the process as their full time responsibilities, but those who do the process can reside just about anywhere!

So next time you hear someone mention the “Change Management people” remember they are talking about the people who are currently using the Change Management process. They might be members of Application Management or the Service Desk, or they might be you!

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…