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: W69J
New Today: 52
New Yesterday: 49
Overall: 146081

People Online:
Visitors: 68
Members: 2
Total: 70 .

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 - Change to be implemented
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Change to be implemented

 
Post new topic   Reply to topic    ITIL Forum Index -> Change Management
View previous topic :: View next topic  
Author Message
rahul_acc
Newbie
Newbie


Joined: Jun 15, 2013
Posts: 4

PostPosted: Sun Jun 16, 2013 1:10 am    Post subject: Change to be implemented Reply with quote

Hi,

Need help to understand...
You have a change to implemented during off-business hours (infra or application) say from 3AM to 6AM (3 hours window). You are doing good for the change, suddenly your team member walks up to you at 5AM and says there is a problem with the change and it may need another 2hours to implement the change. Now the change window needs to extended for another 1 hours. Client is not available during the off business hours to approve another 1 hour time. How to go about it?
My thought - consider the impact of the change. If the impact is huge and there is major disruption to the service if the window goes beyond the approved timeline then we need to backout the change. But the issue here is that even the backout will take time and there are chances that we again overshoot the window. Alternatively, we take the approval from client to extend the window but the client is not available during the off business hours. I understand without prior approval we cannot extend the window. Need to help to understand how do we go about this.
Back to top
View user's profile
Fang
Newbie
Newbie


Joined: Sep 17, 2012
Posts: 13

PostPosted: Fri Jun 21, 2013 6:11 pm    Post subject: Reply with quote

This has happpened to us, and the working solution we are using now is:

We decide a change window when scheduling an approved change. Within that change window we specify the cut off for deciding to back out.

For example: Change shoud take 1 hour. Allow 2 hour change window, with back out go/no go after one hour.

This has resulted in no unexpected impacts on services after complex changes. Obviously, there a simple/fast changes (adding a virtual cluster) where its nonsense to do this!

We are quite open with the business that we are doing this, and no complaints so far................
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> Change Management 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 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.