Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
· Home
· Content
· Feedback
· News
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account


The five ITIL books can be obtained directly from the publisher's website:

Or as downloadable PDFs: HERE

Current Membership

Latest: Alec5350
New Today: 1
New Yesterday: 33
Overall: 231649

People Online:
Visitors: 118
Members: 0
Total: 118



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.

Related Resources

Service related resources
Service Level Agreement

How to set up
IT Change Management
Process Info-Graphic

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.


Select Interface Language:

Please contact us via the feedback page to discuss advertising rates.

The Itil Community Forum: Forums

ITIL :: View topic - Change closure codes
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Change closure codes

Post new topic   Reply to topic    ITIL Forum Index -> Miscellaneous
View previous topic :: View next topic  
Author Message

Joined: Jan 10, 2013
Posts: 3
Location: Melbourne, Australia

PostPosted: Thu Feb 07, 2013 1:08 pm    Post subject: Change closure codes Reply with quote

We have the standard codes:
Backed Out

But I'm wanting to add a code that covers successful changes (ie they fix what they're supposed to or do what they're supposed to) but also cause incidents. ie they weren't properly tested or planned. I was thinking of a code 'successful but caused issues' or similar and didn't know if anyone has implemented something like this?

Making staff choose between 'failed' and 'successful' they're going to pick 'successful' every time, ignoring the ripple effect their change caused as by their recogning it was a success. Having this new code is more likely to be used if it has successful in it.
Back to top
View user's profile
Senior Itiler

Joined: Mar 04, 2008
Posts: 1894
Location: Helensburgh

PostPosted: Fri Feb 08, 2013 7:30 am    Post subject: Reply with quote

Your additional code will allow your staff greater accuracy but the crucial point is what you use the information for. You need a set of codes that will help you to improve your processes.

There are some other threads on this topic:
Definition of Partial Success vs Failure from 2008
Conducting Post-Implementation Review from 2011
Successful change: definition? from 2011
Change failure from 2012

There may be more and I only looked in the Change Management section.
Using "failed" as a code does not do much for proper analysis. For a start do you mean that the implementation failed or that the change did not deliver on its purpose?

Also a change that takes longer and more resources than planned, is still a success by other criteria but you would want to look at the reasons for going over budget and behind the plan.

The same with changes that cause incidents.
"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
Back to top
View user's profile Send e-mail
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> Miscellaneous All times are GMT + 10 Hours
Page 1 of 1

Jump to:  
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

Powered by phpBB 2.0.8 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003

Forums ©


Logos/trademarks property of respective owner. Comments property of poster. Rest 2004 Itil Community for Service Management & Foundation Certification. SV
Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.