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: BereniceP
New Today: 25
New Yesterday: 76
Overall: 142320

People Online:
Visitors: 76
Members: 2
Total: 78 .

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 Freeze - How, When and Why it needs 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 Freeze - How, When and Why it needs to be implemented

 
Post new topic   Reply to topic    ITIL Forum Index -> Change Management
View previous topic :: View next topic  
Author Message
bundera.
Guest





PostPosted: Thu Aug 18, 2005 1:14 pm    Post subject: Change Freeze - How, When and Why it needs to be implemented Reply with quote

Hi

I am a Change Coordiantor and want to know more about Change Freezes. I would like to know how, when and why a change freeze needs to be implemented?

If there is any documentation it would be great to find out where.

thanks

Bundera
Back to top
blackbeard
Newbie
Newbie


Joined: Jan 07, 2005
Posts: 11

PostPosted: Thu Aug 18, 2005 10:00 pm    Post subject: Change Freeze Reply with quote

Change freezes can be used in many ways. Generally speaking ITIL recommends that a change freeze is imposed during business critical activities, these activities are likely to be different for each organisation but could include, Monthly billing runs, Invoice printing, Batch processing jobs or alternatively high profile customer facing activities.
You would impose a Change Freeze in order to avoid any Changes taking place that could potentially have an adverse effect on the Infrastructure which supports the business critical process.

Some organisations that have a scheduled change freeze on the Business Critical Services from 08:00 to 18:00 every working day, so as to minimise disruption throughout the working day.

As for the when, that would depend largely on what information you have from the business, ideally you would have a calendar of business events well ahead of schedule where you could identify times and dates when change freezes are required, this way everyone knows well in advance that they will not be able to make changes at that time and can therefore plan around them.

Other reasons to call for a change freeze, could be prior to a major release to ensure stability during the release, prior to and during an audit, after a major release or a major change to ensure that the release or change has had the desired effect without other changes muddying the waters.

I am sure that there are other reasons to implement a change freeze that would be suitable for other organisations.
Back to top
View user's profile
Guest






PostPosted: Fri Aug 19, 2005 10:50 am    Post subject: Reply with quote

A Change Freeze is called for one reason: to protect the IT infrastructure, application and/or other business activities from any Change activity that may undermine its stability and operation.

The most common times I've seen Change Freezes in action are when a major Change has just been implemented and time is required to monitor the impact of the Change on the infratsructure or affected application. the Change Freeze may be infrastructure-wide (nationally or global) or specific to an application.

The other times I've seen Change Freezes called is over holiday periods such as Christmas or summer holidays. The driver for these is IT's ability to resource Change during these periods. In this situation it makes sense to call a Change Freeze in order to minimise risks.
Back to top
blamblam
Itiler


Joined: Jan 16, 2005
Posts: 37
Location: New Zealand

PostPosted: Fri Aug 19, 2005 10:57 am    Post subject: Reply with quote

Anonymous wrote:
A Change Freeze is called for one reason: to protect the IT infrastructure, application and/or other business activities from any Change activity that may undermine its stability and operation.

The most common times I've seen Change Freezes in action are when a major Change has just been implemented and time is required to monitor the impact of the Change on the infratsructure or affected application. the Change Freeze may be infrastructure-wide (nationally or global) or specific to an application.

The other times I've seen Change Freezes called is over holiday periods such as Christmas or summer holidays. The driver for these is IT's ability to resource Change during these periods. In this situation it makes sense to call a Change Freeze in order to minimise risks.


Sorry... just wanted to add something else to my earlier post in quotes. As with everything around Change Management, it is vitally important that the organisation or affected business unit (if it is a specific Change Freeze) has the reasons for Change Freeze clearly explained to them. It is invariably better to get their buy-in before one is called though most times, everyone will understand why it's been enacted.
Back to top
View user's profile Visit poster's website
Guest






PostPosted: Mon Aug 29, 2005 12:06 pm    Post subject: what is a change freeze Reply with quote

What is a change Freeze???
Back to top
blamblam
Itiler


Joined: Jan 16, 2005
Posts: 37
Location: New Zealand

PostPosted: Mon Aug 29, 2005 12:51 pm    Post subject: Reply with quote

A 'Change Freeze' is a term that denotes no Change activity is to take place whatsoever - all Change activity stops! A Change Freeze can be applied to an entire infrastructure or specific systems or applications.
Back to top
View user's profile Visit poster's website
Skinnera
Senior Itiler


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

PostPosted: Sun May 14, 2006 6:21 pm    Post subject: Reply with quote

Though I've never worked anywhere where all Change activity comes to a stop - it's usually been all planned work, so excluding Fault related work.

We've also taken to callingthem Businness Protection Periods, as that better communicates what their purpose is and sounds less Draconian...
Back to top
View user's profile Send e-mail
Ed
Senior Itiler


Joined: Feb 28, 2006
Posts: 411
Location: Coventry, England

PostPosted: Thu May 18, 2006 5:50 pm    Post subject: Reply with quote

As a Change Manager I can confirm that most Change Freezes are actually moratoriums, in as much as they reduce to almost nil the number of Changes being processed. (All planned/project changes stop)

Most of us will know that there are always things that 'break' during a freeze and that you cannot in all conscience allow the system to run without fixing this problem.

The end result is that you have to allow 'fixes' to be processed and put into place, but because this is a very limited situation, overall control is much tighter.

This in turn ensures that the system is very stable during a period of extreme sensitivity.

Regards

Ed
Back to top
View user's profile
Skinnera
Senior Itiler


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

PostPosted: Wed May 24, 2006 9:22 pm    Post subject: Reply with quote

Though of course there is a view that says if organisations were good at making changes, there'd be a reduced need for a Freeze...
Back to top
View user's profile Send e-mail
Ed
Senior Itiler


Joined: Feb 28, 2006
Posts: 411
Location: Coventry, England

PostPosted: Tue May 30, 2006 6:28 pm    Post subject: Reply with quote

True, but as soon as you introduce those sticky-out bits on the end of arms into the mix, anything can happen, hence the need for a freeze.

Regards

Ed
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.