Please enable JavaScript to view the comments powered by Disqus. Is ITIL 4 Slightly Moving The Focus Away From ITIL Processes?

 

Is ITIL 4 Slightly Moving The Focus Away From ITIL Processes?

NovelVista

NovelVista

Last updated 13/06/2020


Is ITIL 4 Slightly Moving The Focus Away From ITIL Processes?

On the off chance that you've taken any kind of ITIL training preceding 2019, you have without a doubt caught some notice of ITIL processes (Incident, Problem, and Change is the most well-known). In the event that you've taken ITIL 4 Foundation, nonetheless, you likely saw that a significant part of the course material has moved away from processes in favor of practices, value streams, and guiding principles. For the individuals who have constructed their career on actualizing or improving ITIL ideas inside their associations, this is a truly emotional move. 

There are a lot of valid justifications for it, however, which we will investigate further here.

 

ITIL PROCESSES ARE NOT STANDARD ACROSS ORGANIZATIONS

One purpose behind the move away from ITIL forms and the related tools and methods is that there is no one-size-fits-all with regards to, for instance, overseeing changes in an association. There never was, and attempting to give individuals instances of how to run specific procedures had the unintended result of individuals simply doing what the ITIL books endorsed – as opposed to accomplishing the difficult work of imaginatively thinking and talking through what bodes well for their groups, culture, association, and above all, their clients.

HOW A LOPSIDED FOCUS ON ITIL PROCESSES CAN BE UNHEALTHY

Another unintended result the creators of earlier forms ITIL discovered was that associations set an over the top spotlight on working out a couple of ITIL forms, purchasing an IT Service Management (ITSM) stage to computerize said forms, increasing a misguided feeling of accomplishment that they were "doing ITIL," and proceeding onward to some other territory of core interest. Tragically, associations that adopted this strategy to process execution regularly ended up with despondent clients at long last; they despite everything saw IT as simply a fundamental shrewdness, their necessities weren't being met, and at last no genuine authoritative change had occurred. 

In a huge part, concentrating a lot on ITIL forms brings about a nearsighted perspective on a lot greater framework that necessities to change and improve. Anyway, where should our center be? Here are three regions of center in ITIL 4, to be specific that of Practices, Value Streams, and Guiding Principles that supplant the accentuation on procedures and assist us with taking a progressively vital view.

 

SHIFTING FROM PROCESSES TO PRACTICES IN ITIL 4

Probably the greatest move in wording in ITIL 4 is the renaming of procedures as practices. It might appear to be a little move in semantics, however, it's really a truly enormous, and genuinely necessary, correction. How about we start with the meaning of each word:

Process:

  1. A series of actions or steps taken in order to achieve a particular end.

Practice:

  1. The actual application or use of an idea, belief, or method, as opposed to theories relating to it.
  2. The carrying out or exercise of a profession, especially that of a doctor or lawyer
  3. The customary, habitual, or expected procedure or way of doing of something (for example, “current nursing practice”)
  4. Repeated exercise in or performance of an activity or skill so as to acquire or maintain proficiency in it.

Everybody cherishes the pictures evoked by "practice" since what frequently makes associations fruitful is keeping up a continuous spotlight on improving in all territories. Setting up a procedure infers that the action of making the procedure has an endpoint. While training is something we need to continue improving to stay serious and keep on pleasing our clients. 

"Practice" additionally gives us the feeling that we need to work at something like we would a game, and that we will commit visit errors en route – however that is a piece of the learning and improvement process. A training is something groups make a calling out of, sharpening their art more than quite a while. The equivalent is valid with any world-class administration association – Michelin star cafés, top-positioned Conde Nast resorts, and so forth.

 

THE 4 DIMENSIONS OF SERVICE MANAGEMENT IN THE ITIL PRACTICE DISCUSSION

The ITIL 4 books debut a concept called the 4 Dimensions of Service Management, which does a nice job of demonstrating how having processes in place is only one of the many things to consider when approaching how we work. It offers a holistic view of the various areas that are critical to delivering real value.

THINKING BEYOND THE BOUNDARIES OF PROCESS MAPPING WHEN IT COMES TO MANAGING CHANGE

So as to oversee change viably, associations should look past procedure mapping and inspect what it could mean for them all the more comprehensively. Here's a model: Let's say your association is having issues with changes going sideways (which can make groups squander hours pursuing their tails attempting to make sense of what caused a high need issue). IT Leadership chooses it's an ideal opportunity to take a decent, hard gander at the current change procedure and update it to get balance reestablished. To do that, they make a graph like the one beneath. 

This is fine and dandy, however on the off chance that the group stops here, they'll be passing up on a huge amount of chances to make the general act of empowering changes substantially more remarkable. What openings? Envision the amount progressively hearty the change procedure would be on the off chance that they posed a couple of these inquiries:

 

How often should we be making changes?

  • A week after week Change Advisory/Control/Action Board meeting isn't enough. You will need to converse with your clients and see how rapidly changes need to occur – Daily? A few times each day? – and make sense of what that rhythm ought to resemble and how to best suit it. For instance, numerous Agility-disapproved of groups holds Daily Scrums so they can affirm changes every day instead of making their clients hold up a whole week (or more) to actualize a change.

What level of risk are we ok with?

  • This can differ broadly from association to association. For instance, we have a customer that underpins programming on AirForce One. They have, naturally, next to no resistance for hazard. Different associations may not be held to that equivalent standard with regards to keeping away from the hazard and might approve of making, state, crisis switches that once in a while wind up being moved back.

What kinds of changes impact everyone and how do we best discuss them?

  • Conveying the possibility of Daily Scrums forward, I have likewise observed customers hold day by day Scrum of Scrum gatherings, in which an individual group talks about the progressions they'd prefer to make, at that point one individual goes to a short gathering to examine those progressions that sway different groups, so everybody is engaged with the conversation and choice.

Are there alternate change authorities we can use for certain types of changes?

  • What kinds of changes can be peer-checked on and don't have to go to a leading body of individuals?
  • What kinds of changes can be peer-checked on and don't have to go to a leading body of individuals?
  • What changes would we be able to part into littler pieces to decrease chance in any case?

How might we leverage tools that assist us with taking care of more changes and still keep up perceivability into said changes? 

How might we decentralize change choices from a solitary Change Manager or potentially CAB to give more capacity to groups? 

What's the base documentation we can require and for what kinds of changes? 

What basic frameworks would it be advisable for us to lockdown with the goal that changes can't occur stealthily?

In the event that we are utilizing Agile, Lean, or DevOps ideas, has our change group (or initiative group, so far as that is concerned) experienced some fundamental preparing as well as chatted with the groups rehearsing these strategies to perceive how IT can best use thoughts to get change going all the more rapidly while as yet keeping hazard levels at an acceptably low level? 

These are only a few instances of inquiries that might be incited by a greater perspective on different measurements outside of the procedure itself.

 

SHIFTING FROM PROCESSES TO VALUE STREAMS IN ITIL 4

Our preferred idea delivered in ITIL 4 is that of Value Streams, a thought that originates from Lean. IT is frequently so overwhelmed by the in the background subtleties of running the everyday activities of IT that they miss the scaffold that permits them to convey all the more obvious with clients. Having a comprehension of how Products and Services added to the association in general and how the association conveys an incentive to end clients is basic. Rather than IT serving different specialty units (as appeared in the principal outline beneath), the better method to imagine Value Streams is the manner by which each specialty unit meets up to serve the association's clients. 

IT in support of other inward specialty units: 

Procedures make up esteem streams, yet they are one level lower than what is delineated here; and in the event that we keep on concentrating exclusively on singular procedures, we will miss the opportunity for a larger (and more productive) conversation with the overall organization. See our blog post for more information on Value Streams.

SHIFTING FROM PROCESSES TO GUIDING PRINCIPLES IN ITIL 4

Another idea that understudies, clients, and professionals the same have battled with during that time is the manner by which to approach executing ITIL ideas in their associations. This was particularly evident in ITIL v3 preparing, where understudies took in an astounding 26 ITIL forms. It made the possibility of execution scary and befuddling. In 2016, the ITIL writers distributed the primary form of the Guiding Principles, and they've been additionally defined as a component of the ITIL 4 books (see the graph underneath). The explanation these are so significant, and in our view, more significant than covering the means that help a specific procedure, is that much the same as with the Agile development, there's "Being Agile" versus "Doing Agile." ITIL's Guiding Principles fit decisively into the "Being ITIL" classification. Our attitude, qualities, and convictions drive our activities in enormous manners, similar to how we approach ITIL ideas in any case, just as how we create and, at last, convey top-notch, important items and administrations that take care of issues and push our associations ahead. And that's what our ITIL 4 training programs teach you. Check out what all we have in store now!

Topic Related Post

Is ITIL certification worth your time & efforts?
Is ITIL certification worth your time & efforts?
How to implement ITIL?
How to implement ITIL?
What are the Most Common Root Cause of Major Incidents?
What are the Most Common Root Cause of Major Incidents?

About Author

NovelVista Learning Solutions is a professionally managed training organization with specialization in certification courses. The core management team consists of highly qualified professionals with vast industry experience. NovelVista is an Accredited Training Organization (ATO) to conduct all levels of ITIL Courses. We also conduct training on DevOps, AWS Solution Architect associate, Prince2, MSP, CSM, Cloud Computing, Apache Hadoop, Six Sigma, ISO 20000/27000 & Agile Methodologies.

 
 

SUBMIT ENQUIRY

 
 
 
 
 
 
 
 
 

Upcoming Events

ITIL-Logo-BL
ITIL

Every Weekend

AWS-Logo-BL
AWS

Every Weekend

Dev-Ops-Logo-BL
DevOps

Every Weekend

Prince2-Logo-BL
PRINCE2

Every Weekend

Topic Related

Take Simple Quiz and Get Discount Upto 50%
     
  18002122003
 
  
 
  • Disclaimer
  • PRINCE2® is a registered trade mark of AXELOS Limited. All rights reserved.
  • ITIL® is a registered trade mark of AXELOS Limited. All rights reserved.
  • MSP® is a registered trade mark of AXELOS Limited. All rights reserved.
  • DevOps® is a registered trade mark of DevOps Institute Limited. All rights reserved.