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

Current Membership

Latest: MelvinLok
New Today: 45
New Yesterday: 49
Overall: 148389

People Online:
Visitors: 44
Members: 0
Total: 44

Languages
Select Interface Language:


Major ITIL Portals
For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone

Related Resources
Service related resources
Service Level Agreement
Outsourcing

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.


The Itil Community Forum: Forums

ITIL :: View topic - Successful change: definition?
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Successful change: definition?
Goto page Previous  1, 2
 
Post new topic   Reply to topic    ITIL Forum Index -> Change Management
View previous topic :: View next topic  
Author Message
Skinnera
Senior Itiler


Joined: May 07, 2005
Posts: 121
Location: UK

PostPosted: Fri Jan 04, 2008 6:54 pm    Post subject: Reply with quote

For my organisation, I have defined a Successful Change as follows;

A Change that was implemented and satisfied its prescribed criteria by meeting all of the following conditions:
• Delivered fully what was expected
• Fixed what it should have
• Did not have any unexpected impact on service
• Did not have to be backed out.
• Did not over-run its Change Window

However we are just about to move to a very different model, which does away with Successful and Failed in favour of these more informative options;

Implemented - No Impact
Implemented - With Impact
Backed Out - No Impact
Backed Out - With Impact

These are less subjective and emotive, and accurately describe exactly what happened at the end of the Change's lifecycle.
Back to top
View user's profile Send e-mail
Ines
Newbie
Newbie


Joined: Mar 21, 2006
Posts: 18

PostPosted: Tue Jan 15, 2008 1:24 pm    Post subject: Reply with quote

[quote="Chilly]The possibility that an incident may occur, may be a known risk. It may be very likely that when you cut over the core router, you will recieve some incident calls from users saying they can't access the system.[/quote]

It may be a known risk, but it doesn't mean stakeholders are happy to wear it if it happens. IT's not like you would make a change, it break something, and leave bits broken. You would fix the broken bits. Those risks still need to be mitigated.

A successful change should not require utilisation of a backout plan, or additional resources, time and effort than that documented in the implementation plan. Everything should still work as though the change never happens - key phrase is that it should be "seamless to the end user".
Back to top
View user's profile
TomG
Newbie
Newbie


Joined: Apr 06, 2011
Posts: 3

PostPosted: Thu Apr 07, 2011 5:06 am    Post subject: Compromise between Successful and Failed Reply with quote

Chilly and Ed, great back and forth. I struggled with the same topic a few years back and so I introduced a classification of, Successful With Problems.

Call it what you will, there was a need to capture changes that were implemented to plan and gave the requestor/benefactor/stakeholder what they wanted but an issue appeared in production that was otherwise unforseen.

There's usually no easy way to capture these types of occurances but the few that did get caught were quickly classified in our change reporting and since I held the problem manager title, I bypassed trending it because there weren't enough to be trended and went right into problem analysis and gathering info.

As for a successful change definition, my criteria matches that of the posting from Skinnera with slight modification.

Whatever criteria you choose to define a successful change, my advise based on learning for past mistakes is to ensure you involve your CAB members and process sponsors in designing them and to get buy in. You'll need this upper management support and CAB support when your assessments or the change results are challenged by those who don't want to be measured because they will have a perception that they need to defend themselves if anything perceived as negative arises.

My first post.... hope I'm not off my rocker... I love this kind of stuff.
Back to top
View user's profile
Pixxolo
Newbie
Newbie


Joined: Aug 05, 2011
Posts: 1

PostPosted: Sat Aug 06, 2011 4:56 am    Post subject: Reply with quote

Hi All.....please advise on this....

Here is the example:

RFC is submitted and approved for Date X @ 21:00.
RFC is communicated and scheduled on a Forward Schedule of Change Calendar….effectively ‘reserving’ that date/time.

The implementation date/time passes without any change being made and no notification to Change Management.

Question:
Should the RFC be marked as FAILED?
Back to top
View user's profile
noneforit
Newbie
Newbie


Joined: Jul 30, 2010
Posts: 18

PostPosted: Mon Aug 08, 2011 11:42 pm    Post subject: Reply with quote

What does your CM process define as a 'Failed' change

We currently use 'Sucessful' and 'Unsucessful'

Using your example, that would be an unsucessful change according to our definition

They said they were going to do XYZ at a particular time and they didn't do that, so would be an unsucessful change

The change itself hasn't failed (as in gone wrong) but it has failed to happen so it would be down to how you define a failed change
Back to top
View user's profile
Diarmid
Senior Itiler


Joined: Mar 04, 2008
Posts: 1884
Location: Newcastle-under-Lyme

PostPosted: Wed Aug 17, 2011 4:53 pm    Post subject: Reply with quote

Does it matter to your management whether a change (not an RFC) has failed or has not been applied?

Is such high level and undefined information of any value? Can you make use of it/
_________________
"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 -> Change Management All times are GMT + 10 Hours
Goto page Previous  1, 2
Page 2 of 2

 
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 http://www.nukecops.com

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.