Friday, February 15, 2013

Change Management - The 7 R


ITIL change management recommendations emphasize the activity of assessing and evaluating the change requests or change orders. During change assessment, some generic questions, popularly known as 7 Rs of change management, play critical role in judging its potential impact on service assets and configurations. It includes two ‘who’s – who raised the change request/change order and who is responsible. And five ‘what’s – what are the reason, return expected from change request, risks involved, resources required and relationship with other change order or change request (either in pipeline or executed).

WHO is the Requestor ?
WHO is Responsible for the build, QA and final change implementation?
WHAT is the Reason - what necessitates the change?
WHAT is the expected Return from the change?
WHAT Risk factors are associated with the change?
WHAT Resources are required to execute the change?
WHAT is the inter- Relationship between this change and other changes?

It is necessary to bear in mind that ITIL Change Control methodologies cannot effectively work in isolation and is a part of the integrative and interactive forces of IT service management. The ITIL Change Management module works seamlessly with the wide network of its partner service management components and the process interfaces like the CMDB or Asset and Configuration Management, IT Service Continuity Management, Request Management, Service Desk, Capacity and Demand Management, Release and Deployment Management and even with Knowledge Management processes. For example, an incident may lead to a change request and that change may require some CMDB change in terms of modification of some attributes of a CI; or it might alternatively bring a new CI in the CMDB database resulting in a new service enlisted on 'Service Catalog' and spawning associated access requests for that service through request management module.The new services, thus created, may also necessitate the associated SLA or SLO requirement.

Now, this does not mean that in absence of desired integration with the associated component services, it is not meaningful to start implementing ITIL change management processes. It is always necessary, for a start-up or a not-so-matured IT setup, to have a defined process-flow, procedure and guidelines for IT Change Management (in contrast with having no process at all in place), though initially it might not be hundred percent compliant with the ITIL framework.

No comments:

Post a Comment