Skip to main content

ISO 20K Can Be a Starting Point, Not a Destination

Since it's adoption, there has been a slow, but steady growth in the number of organizations that are seeking, or have achieved, ISO/IEC 20000 (ISO 20K) certification. For the most part, interest in the standard is being driven by RFP requirements or perceived competitive advantage. The certificate is seen as an "award" that an organization receives for achieving best practice ITSM. While ITIL is being actively adopted, many organizations are overlooking ISO 20K because they do not perceive any value in the certification.

I recently realized that we are looking at ISO/IEC 20000 in the wrong way. The standard has so much more to offer than just a certificate. It actually provides a starting place for an ITSM journey, not only the
destination.


ISO/IEC 20000 defines the "minimum critical activities" required to deliver high quality, aligned services. Once these activities are understood, an organization can assess which activities they already execute well and which may need implementation or improvement.

Here are some other benefits of ISO/IEC 20000:

  • It is succinct and easy to understand ("you shall record all incidents")

  • It applies to every internal or external IT organization regardless of size or industry

  • It distinguishes critical ITSM activities (in Part 1) from recommended activities (in Part 2)

  • It logically groups processes (Resolution, Service Delivery, Control, Relationship, Release) so you can build related processes together

  • It includes a Quality Management System with requirements for Management Responsibility, Training/Awareness/Competency, Documentation and Plan-Do-Check-Act

  • It is founded on continual improvement

  • It is objective and measurable and can help diffuse political or cultural challenges

There is no requirement that you adopt ITIL in order to implement ITSM according to ISO 20K. ITIL does offer a wealth of good knowledge that conforms to the standard. However, you can also cherry-pick guidance from other frameworks such as MOF or Cobit. Microsoft recently released a free Using MOF for ISO/IEC 20000 whitepaper. You can also meet the standard's requirements through successful, conformant, internal practices.

Whether you are at the beginning, underway or mature in IT Service Management, I would highly recommend learning more about the standard. It is available as a formal standard, digested ISO/IEC 20000 pocket guide or in several ISO/IEC 20000 books.

EXIN has also created a qualification scheme for ISO/IEC 20000 training and certification. You can explore the scheme at www.takeanotherlook.it. At the very least, I would recommend the ISO/IEC 20000 Foundation course for key staff involved in your ITSM implementation.

Striving for ISO/IEC 20000 certification is a management decision; using the standard as a tool for successful ITSM is just good management.

Comments

Jayne Groll said…
Ed Williams wrote an interesting blog that elaborates on this topic even further. Check it out at http://itsmadviser.com/portal/index.php?option=com_wrapper&view=wrapper&Itemid=4
markinson said…
Reading this post I completely agree with the topic.I mean that's true it is just the begining....
ITIL Version 3

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…