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

Usecase Scenario development and User Stories

A common comic mail circulates with this image, which gives good understanding of how requirements captured during a project life cycle goes like this: Typical Software Development Life-cycle explained Above picture succinctly tells about common perception of developing a software, how requirement understanding filters with changing roles, time and space with gaps between factual and results. Thanks to the the word "agility", which has evolved in world of software technology with the evolution of Rational unified process the term use-case or scenario development for documenting and capturing requirement in the initial phase of software development. "A use case is a software artifact of systems and process of expected sequence of interactions between a module and an external actor, which leads the actor to desired goals and objectives. " Use case scenarios can be mirrored as clip of a movie making scene development where-in director has assigned a s...

Games People Play in context to Projects

Games People Play in context to Projects: Contextually life and projects full of games, work on dynamics of human relationships by Dr. Eric Berne guides us not only in many social but relationship situations in corporate world also. In Todays concurrent world where we are living in a global village with Orkut, Facebook, Linkedin, Twitter and other social media leads to discounts of information in social network, where more of transactional games played knowingly(conscious) or unknowingly(unconscious). Precede to this let us understand game, A game full of transactions played with different roles by players changing their roles for a outcome in different ego states like Parent, Adult and Child ego states that will payoff. Continuing with Payoff, specifically in context to Project teams where transactions happen at concrete or transformational levels where people not necessarily behaving rationally and motivat...

Understanding Business Value of IT(Information Technology)

Is IT driven by business? I believe its a good question to be asked at this point in time after the doom of financial markets allover world. When top investment banks collapsed in USA and Europe everybody is asking a question how it is possible if the system in place. IT in general supposed to be driven by business requirements so its natural process that, as other component in business, this is also adding value to business, but is that benefits realized to business? Is IT a hype from time and again? Business value of IT measured in different metrics and methodologies that may or may not give true picture of IT value to business, so the contradiction lies in the hypothesis itself that IT is driven by business which is adding no value but continuing. In the concurrent world where businesses are competing for survival and existence IT is invaluable from intangible perspective. Making sense of PM triangle The infamous scope, cost and schedule trio can be realized for IT bus...

Project Portfolio-Program Management

Search This Blog