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: JulietU86
New Today: 3
New Yesterday: 67
Overall: 148462

People Online:
Visitors: 56
Members: 1
Total: 57 .

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

Change Freeze Types?

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


Joined: Mar 15, 2012
Posts: 2
Location: Scottsdale, AZ

PostPosted: Fri Mar 16, 2012 8:27 am    Post subject: Change Freeze Types? Reply with quote

Hi All,

I was recently tasked with looking into change freezes, I know many of them lock the entire system down, but I wanted to see if anyone has had any experience with pinpoint Change Freeze (by application, environment, etc)

What are the positive and negative aspects of it?
Back to top
View user's profile Visit poster's website
Diarmid
Senior Itiler


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

PostPosted: Fri Mar 16, 2012 9:51 am    Post subject: Reply with quote

A change freeze is more of a psychological prop than anything else. It is a way of emphasising that there is high risk and/or cost in allowing changes for some period for some reason.

It may be because of a holiday period when company policy allows a thinning of staff for a few days, leaving, say, some support areas vulnerable. It may be because there is critical activity going on in some business area and this dare not be interrupted.

In reality, the "freeze" makes it much harder to justify any change at that time. Harder, but not impossible. A situation can arise requiring a change for a more important reason than the "freeze", even if the risks are greater than normal.

So long as the reason for the "freeze" is understood clearly, then it seems logical to confine it to the areas affected (even indirectly, perhaps) by that reason.

In theory there is never a need for a freeze. In theory the risk assessment of any proposed change should recognize and take into account these temporary additional risks. So, advertizing a "freeze" may save a little resource by discouraging change requests, but not much because these changes have to be put through the mill some time and it is mostly the scheduling that will be affected.

An interesting area is so-called "standard changes". If these have been used as a way round the change protocols and have not been put under their own defined processes, then the announcement of a "change freeze" may be the only effective way to prevent them going ahead willy-nilly. This could even be a reason for announcing a global "change freeze" just to be sure.
_________________
"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
Lokaj
Newbie
Newbie


Joined: Mar 15, 2012
Posts: 2
Location: Scottsdale, AZ

PostPosted: Wed Mar 21, 2012 4:07 am    Post subject: Reply with quote

So if its a psychological prevention, then if the application, environment, or enterprise it makes no real difference in the eyes of ITIL as long as the process itself is following the necessary procedures. So moving this forward as a company to allow more narrow focus when specific areas or products are having difficulties.
Back to top
View user's profile Visit poster's website
Diarmid
Senior Itiler


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

PostPosted: Wed Mar 21, 2012 4:35 am    Post subject: Reply with quote

ITIL has no eyes. It is your own review and audit activities that have eyes. They can determine if what you have done is appropriate and effective.

I'm not at all sure that the ITIL books even mention "change freeze", but I am sure that they say nothing prescriptive about it. It is really not an ITIL issue.
_________________
"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
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.