Skip to main content

ITIL 4 – Why and Why NOW?


To Understand Why and Why NOW, I will use some of the “Guiding Principles” that are the golden chords steaming through all practices defined in ITIL 4. These guiding principles are themes throughout the concepts and precepts that were discussed in a recent ITIL 4 Foundation certification class. Practitioners and thought leaders gathered together from all over the world to discuss and learn more about ITIL 4 best practices There are seven guiding principles discussed in ITIL 4. I will begin with these three to answer the question: Why and Why Now?


Focus on Value

ITIL 4 is a holistic approach for managing value. Based on the Service Value System and the integration of dimensions that tie together practices, ITIL 4 enables speed to value for all service providers. Value is the results of all of our people, practices, and technology. Value is what we deliver. ITIL 4 stresses the need to co-create value with all stakeholders none more important than with the customer. If we are going to succeed, we must all “Focus on Value” 



Start Where You Are
In the words of Donna Knapp, we need to “honor the past”. There has been a lot of effort and real commitment that has been put forth to advance product development and service management in every organization. We certainly do not want to throw the baby out with the bath water. Honor the past and leverage from gains made in ITIL V3, DevOps and Agile initiatives. ITIL 4 is taking a gradient approach to development and so far, it has in my opinion “Overdelivered”. 


Progress Iteratively with Feedback

Organizations must shatter the silo’s! When we hear solo’s we typically think of organizational or departmental silo’s and that is true, they must be shattered! But, what about siloed practices, siloed tools, different and siloed agendas? These too must be shattered if we as an industry are really going to optimize. Taking an iterative approach to transition the way we think and the way we do work, allows for faster delivery of value, fast feedback and most importantly the ability to take FAST corrective action along the journey to optimize our effort. 

These guiding principles are not only stressed in ITIL 4 to support the “Service Value System” but can truly be the golden chords and the glue that pull it all together for staff, for teams and most importantly for those that are the recipients of “VALUE”! Principles and practices of ITIL 4 bind together to enable and support, Agile, Lean and DevOps initiatives.

So as it relates to ITIL 4; Why, and Why Now? For some, the answer is simply to compete, for others it is to increase revenue through quality of service. For some, it is a choice that could make all of the difference! What worked in the past will not work in today’s fast-moving world. For some, the choice to adopt and adapt to ITIL4 best practice will be survival!

Stay tuned to the ITSM Professor to learn about ITIL 4 and other Guiding Principles! 



… educate & inspire!

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…