Skip to main content

Conducting an Internal ITSM Asssessment

One of my followers recently asked about approaches to performing an organizational ITSM assessment.  I’ve summarized some of his questions:

1.      While surveys, interviews and workshops are assessment methods, would focused interviews with individuals pertinent to the process being assessed be a good approach? 

2.      Should my final assessment score for a process be an average of several people’s maturity level ratings on that process?

3.      Should my assessment only include participants who are directly involved with that process?

Assessments should take a well-rounded approach to gathering information, input and feedback.  It’s not a one-size-fits-all.  If you have the ability to conduct one-on-one interviews with key stakeholders, that’s a great way to encourage dialogue through open-ended questions.  While the results may not be as measurable as some other assessment techniques, interviews provide the unique opportunity for deeper probing and follow-up.  Surveys and workshops also have a place in assessment – they are excellent vehicles for getting input from large and diverse groups of stakeholders.  Like any good recipe, an ITSM assessment should include different ingredients.

A well-rounded approach should also include engaging a large cross-section of stakeholders from the business and IT. Each will touch the process in a different way – some may execute or contribute to process activities, some may be recipients or customers of the process, others may be observers of the process results.   The more perspective that you can garner during the assessment, the better. 

As for scoring, I would suggest that the narrative is more important than the number.  Appendix H of the Service Design publication explains ITIL’s Process Maturity Framework.  While the levels are numeric, the descriptors are not assigned a value.  This approach encourages the assessor to focus more on what’s happening with the process and less on what score to assign.    Process maturity is not an exact science, but it can be an invaluable asset when performing an ITSM assessment.

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…