Changes to IT services fall in the category of common activities. No matter how efficient the Change Management process is, it\u2019s no secret that mistakes happen during change implementation. Some occur for good reason, while some mistakes are hardly explainable. That puts greater significance on the efficiency of the Change Management process.<\/p>\n
An efficient Change Management process means that you have control from the beginning through the end of change implementation. Let\u2019s focus on the end of the implementation. What if change<\/a> implementation doesn\u2019t end as expected? What if it goes in the wrong direction and you need to back out to the state before the implementation began? Both ITIL<\/a>\u00a0and ISO 20000<\/a> have answers to that question.<\/p>\n No matter whether you implement ITIL or ISO 20000, one of the basic postulates of the Change Management process is that there shouldn\u2019t be changes that are implemented<\/a> without authorization. That could be on a local level (e.g., a network admin authorizes standard changes) or on the highest level in the organization (e.g., Board of Management for major changes). The article ITIL V3 Change Management \u2013 At the heart of Service Management<\/a>\u00a0can help you understand the basics of the Change Management process and authorization of changes. Before authorizing the change, the change authority (the person or group who is empowered to authorize change<\/a> of a particular type) needs to ensure that there is a plan to revert to the initial state if change implementation is unsuccessful.What are they?<\/h2>\n
\n