Skip to main content

Simplifying ITIL for ITSM

Simplifying ITIL one by one:

ITIL V3 best-practice guidelines across the five stages of the service life-cycle are
complex in nature and understand to interpret. ITIL libraries are abstract and didn't provide implementation details.

The ITIL process framework concentrates
on the service lifecycle and the how that service management components are structured and linked in that framework. It personifies road-map for IT companies that are looking to improve on service quality levels and align more closely with business objectives to create value for their clients.

Process Improvement Program(PIP):

PIP a small concept but have larger impact, Process improvement program designed on multiple aspect of any process with a Plan-Do-Check-Act (P-D-C-A) steps and a strong feedback mechanism will make process pitfalls to more robust. Looking from the microscopic level at any of the existing process in an organization from concept of PDCA cycle and multiple checks will increase the probability of success for PIP which can be applied as generic template for any of the existing processes.

Take one : Availability Management

Availability Management focuses organizations to make happen the IT service-availability to support the business functions both as a customer and service provider.

Availability Management facilitate the contract of performing certain functions on a continuous basis for period of time. It also gives a entitlement of sustainability, maintainability,  reliability, up-time and downtime, backup of services to be restored in contingencies and at the same time security of data from any threat.

Above practices requires quantity and quality of people and technology in sync to get best results. Obviously ITIL is a structured framework, which provide certain way of acting and handling operations but not necessarily an out of the box solution to a problem.

 
 P.S.:
The IT Infrastructure Library originated as a collection of books, each covering a specific practice within IT Service Management. ITIL was built around a process-model based view of controlling and managing operations often credited to W. Edwards Deming and his plan-do-check-act (PDCA) cycle.
 

Comments

Popular posts from this blog

Porter's outside-in and Hammel - Prahald's Inside-out

Over the years inspiration and motivation to out do something which creates spark in the genre of concurrent times is always been challenge for all of us, to make things happen requires a plan, an out of the box solution to rationalize its existence. More often than not inspiration are unknown to us, which may leads to different scenarios of multiple ways of looking at things differently and indifferently also, anyways there are always n-1 degrees of freedom to think differently for n+1 different ways looking at things. Inspired by a spiral which is coincidentally a galaxy in our spatial system gives us views like --if one start from a point from outer end to reach at center, will reach from outside-in and if one starts from the center and circle outwards move than that will be inside-out thinking. So again its up to individuals, which way move. Traveling by we see stars and other objects binding each other with gravitational forces. Galaxy One of the many management stra

Constructive Blame storming and using Devils Advocate in problem solving and competency development

Cover of Six Thinking Hats Discussions leads to solutions , mistakes leads to innovations, As part of innovation , solution approaches, models quite often used technique in healthy discussions on day to day basis is Brain Storming , mischievously known as blame storming. To the extent organizations build competency around subjects of real time situations, till it takes to materialized very few of them make it to the concrete implementations. Take for example Google revolutionized the way we use internet with countable team, that storm sustained and now second wave coming from Facebook, Linked etc. Questions asked about their revenue models but skepticism will always there, social networks are strong tools not only for marketing but of communication, collaboration, and increased productivity and realized intangible benefits. Discussions are full of Arguments, counter arguments, statements, facts, thesis, anti thesis etc. Contextually the term devil's advocate can be dis

Frisking out project risk

Risk Management road sign (Photo credit: Wikipedia ) So what is a risk ? First understands and identify a risk is most important part of risk management.A risk is a probability of uncertainty associated with executing certain item/task/process/work etc.  A risk generates out as soon as we initiates a task. A critical resource in terms of skill set, in a team is a potential  risk of leaving the project in between because of unavoidable reasons. So a risk is inevitable, only thing we can do is ; manage and mitigate. Just like handling/catching error in software program . Always plan for the element of risk in project from the start and reiterate control over it for any contingencies. Steps to assess risk: Identify---------->Analyze--------------> Set priority to each risk Steps to control risk: Mitigate------------>Plan for contingency----------> Quantify it and Set a control process Design a Solution process at the team level: Taking help of the experts inv