ITILv3 changes management

These days almost every business is facing varying conditions, everlasting oppositions as well as enlarged customer necessities.  To remain economical and practicable, their IT and service organizations must be in complete attachment with the tactical objective of the company. This means information technology has to be an affiliate in conveying value to the consumer. Whereas no tactic can assure comprehensive accomplishment, a consistent Change Management procedure with manifestly definite duties as well as responsibilities strengthen the chances that the business goals are efficiently attained and limits the chances of costly and upsetting mistakes in implementation. There are some crucial tips mentioned below that you should use while applying the ITIL Change Management procedure.Initiate Change RequestYou can initiate New Change Request or initiate a change from one or more Problems. The Request for Change is considered based on the Business Impact, Urgency and Priority. The Change plan is formulated to get started with a the change processThe Change Plan needs to have complete details about the reasons for considering the change, how this change can impact business. The Change Planning stage needs to have following information so that Change Managers and CAB has all the detailed to make informed decisions.Impact Analysis - risk involved in implementing the changeRollout Plan - how the plan will be implementedBack out Plan - plan to restore things to back to original state if plan failsChecklist - List of mandatory items required for the plan to succeedStandard Changes are pre-approved changes authorized by the Change Manager based on Management policies. Frequent changes such as permitted RAM upgrade to users or list of allowed software applications can be pre-approved by the Change Manager so that changes are fulfilled faster.Minor ChangeA Minor change is defined as a change that has low impact on business and does not consume lot of resources. The Change Manager approves the Minor Changes.Major and Significant ChangesMajor and Significant Changes need the approvals from all the members of the Change Advisory Board and the Change Manager. The members of the CAB (Change Advisory Board) are determined based on stakeholders who will be affected by the change. Based on the change plans and risk involved the CAB members will vote and recommend to Accept or Decline a change plan.What is the ‘Normal’ change? ITIL version 3 has now introduced the concept. It actually follows full blown of ITIL Change Management process- authorization, assessment, scheduling before implementation and CAB approval. Based on the complexity, scope, and impact, the normal change is further categorized as the major, minor, and significant ones. The ITIL emergency change is highest priority change, which is defined in the organization. The emergency changes are actually defined as the changes that have to get evaluated, assessed as well as rejected or approved in the short period of time. Emergency Change is actually reserved for the changes planned to repair the error in the IT service, which is negatively impacting business to the high degree.Just defining the change as emergency doesn’t automatically entail change must get implemented. Emergency Change Advisory Board can assess change and give advice to delegated person liable for approving and rejecting the emergency changes. In context of ITIL, ‘change priority’ has to be rightly computed prior to scheduling these requests. Formula for determining the Change Priorities is: Priority and Business Impact with Urgency.