Failed change clarification

Discuss and debate ITIL Change Management issues
Post Reply
User avatar
jyan08
Newbie
Newbie
Posts: 1
Joined: Mon Jul 01, 2013 8:00 pm

Tue Oct 29, 2013 7:30 am

When should we classify a change as failed?
should a change resolve the issue to be successful? (if the change is not the solution to the problem, should it be tagged as failed?)


User avatar
UKVIKING
ITIL Expert
ITIL Expert
Posts: 3639
Joined: Fri Sep 15, 2006 8:00 pm
Location: London, UK

Tue Oct 29, 2013 10:41 am

What ever your own Change Management process and policy deem as the definition of a failed change is

It is actually up to you
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
User avatar
zenbubble
Newbie
Newbie
Posts: 3
Joined: Wed Apr 06, 2011 8:00 pm

Tue Apr 01, 2014 1:28 am

I use a number of Change closure codes - Hopefully this may help:

SUCCESSFUL: Change ran to plan and achieved it's objectives.

SUCCESSFUL WITH ISSUES: Change achieved it's objectives, but did not run to plan (ran over time, required extra, unplanned steps, etc)

CANCELLED: Change was never implemented. Must be declared CANCELLED before it's planned start date/time

FAILED: Change did NOT meet it's planned objectives

BACKED OUT: Change did not meet it's planned objectives, and introduced issues into the environment requiring that the change be backed out and the environment returned to it's previous, baseline state.

Home this helps. Your mileage may vary.

-Chris
User avatar
ChangingMan
Itiler
Itiler
Posts: 27
Joined: Sun Apr 27, 2014 8:00 pm

Tue Apr 29, 2014 4:02 am

zenbubble wrote:I use a number of Change closure codes - Hopefully this may help:

SUCCESSFUL: Change ran to plan and achieved it's objectives.

SUCCESSFUL WITH ISSUES: Change achieved it's objectives, but did not run to plan (ran over time, required extra, unplanned steps, etc)

CANCELLED: Change was never implemented. Must be declared CANCELLED before it's planned start date/time

FAILED: Change did NOT meet it's planned objectives

BACKED OUT: Change did not meet it's planned objectives, and introduced issues into the environment requiring that the change be backed out and the environment returned to it's previous, baseline state.

Home this helps. Your mileage may vary.

-Chris
Great deffinitions there, although I would say if a change was backed out, it failed.
User avatar
viv121
ITIL Expert
ITIL Expert
Posts: 117
Joined: Fri Dec 14, 2007 7:00 pm

Wed May 21, 2014 7:00 am

I would agree that a backed out change has actually failed to deliver its objectives.
regards,

Vivek
"the only statistics you can trust are those you falsified yourself"
Winston Churchill
Post Reply