Skip to main content

Happy Birthday ITIL!

ITIL is turning 25 this year. 

In honor of this milestone, AXELOS commissioned a study (The Importance of ITIL® – A Global View – 2014 and Beyond) to provide a global and independent assessment of the current perception of ITIL, engaging nearly 400 C-Level and medium tier service managers in key international regions across a range of industries.

One of the stated reasons that the study was commissioned is because ITIL’s benefits are being questioned in light of factors such as cloud computing, more advanced automation, and agile. The results of the study reaffirm ITIL’s value, particularly in the eyes of IT executives. In fact, according to the study, just under 70% of executives indicated that ITIL is becoming more important in light of these trends.

Some interesting results include:
  • 71% of those surveyed view ITIL as playing a tangible role in supporting the move to DevOps and Agile 
  • ITIL 2011 adopters are more likely to see ITIL as growing in importance
  •  40% of non-2011 respondents plan to move to 2011 soon 
  • Certification and training was deemed the most valuable resource even over the core books 
  •  43% of respondents specified ‘too busy’ as their reason for not taking ITIL training 
  • We still have a ways to go …only 21% of the organizations surveyed had achieved ‘improved agility and flexibility in provisioning services’ through ITL.  That's where DevOps and Agile Service Management(r) will play an important role
To address the issues of improving agility and flexibility, my colleagues at ITSM Academy are excited about the upcoming DevOps and Agile Service Management certification courses.  Stay tuned!




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…