Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.
NOTE: ® ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.
Search
Languages
Select Interface Language:
Advertising
Please contact us via the feedback page to discuss advertising rates.
The Itil Community Forum: Forums
ITIL :: View topic - Classification of Emergency Changes
Posted: Wed Dec 18, 2013 8:31 pm Post subject: Classification of Emergency Changes
I am trying to classify the emergency changes that took place within this year to determine if these emergency changes could have been prevented. I have come up with just 3 classification names and was wandering if there is more areas that I could include in this list.
List:
Insufficient Testing
Insufficient Planning
Incorrectly logged as a ERFC
Joined: Sep 16, 2006 Posts: 3589 Location: London, UK
Posted: Thu Dec 19, 2013 1:12 am Post subject:
Nizmo,
I can provide you the following values -
Requester cant plan
Requester wont plan
Requester's plan was not based on reality
Requester is a complete (incomplete) idiot
WTF ?
However, while that is humorous (to me at least), the list of values for E CABs and why they are happening needs to be based on the situation in your organisation.
Look at the ECAB, look at the reason given.. if there is one. If not, start requiring one. _________________ John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter
Posted: Fri Dec 20, 2013 12:40 am Post subject: Classification of Emergency Changes
Hi,
One way to minimize the changes is to ask several questions to ours "customers" in a way they begin to think if that change is really necessary.
Some examples:
- Why change
- Describe present state
- Describe future state
- What will change
- What will not change
- Risks during change process
...
You can have many classifications depending of your business.
Some examples:
Hardware
Application Software
System Software
Network
...
or generic:
Low: this change may be best made alongside others, such as when updating software packages, buying new hardware, etc.
Normal: This change should be made provided it does not get in the way of another, higher priority, change.
High: a change that should be made without delay, as it is associated with known errors that are significantly degrading service quality. The CAB should assess this change at its next meeting and take the relevant measures to enable a rapid solution.
Urgent: this problem has to be solved as it is causing an interruption or serious degradation to service. An urgent change triggers the so-called emergency change process, which we will deal with separately.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum