Dissecting IT service management (ITSM) Model in Mid Size companies

IT service management (ITSM) Model and its effectiveness:

In today's Agile environment where clients needs and fast changing business environment keeps service delivery on top of the minds of CIO, over a period of time many frameworks have grown up as part of service delivery management which have standardized as well like ITIL (IT Infrastructure Library) that guides us in delivering services with quality and efficiently which satisfy client needs and demands.

ITIL objective focuses on implementation of delivery model and how efficiently we can optimize resources to best availability to infrastructure and other services offered. ITIL encompasses as structured framework which has five elements as part of service life cycle named as Service Strategy, Service Design, Service Transition, Service Operation, Continual Service Improvement. Now the question is how these elements be accommodated in day to day operational level implementation.

Above listed service life-cycle elements can be customized according to organisation needs which again energized with six sigma, and other control methods. At the more granular level it has been further categorized into several criteria which are named as in ITIL V3 like Availability Management, Problem Management, Capacity Management, Release & Deployment Management, Change Management, Request Fulfillment, Event Management, Service Asset & Configuration Management, Financial Management, Service Catalog Management, Incident Management, Service Level Management, IT Service Continuity Management, Service Portfolio Management, Knowledge Management will be used as per organization suitability metrics.

Obviously these terms looks quite abstract in nature but can be deciphered at more specific requirements at times needed but in general it provides a governance framework as part of service delivery management with effectiveness in many ways.

Comments

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

Project Portfolio-Program Management

Search This Blog