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: LatashiaDA
New Today: 15
New Yesterday: 37
Overall: 231700

People Online:
Visitors: 120
Members: 0
Total: 120



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 - Inclusion of all changes in the CM process
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Inclusion of all changes in the CM process

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

Joined: Oct 16, 2006
Posts: 2

PostPosted: Tue Jan 30, 2007 12:39 am    Post subject: Inclusion of all changes in the CM process Reply with quote

This is my first post in this forum. I am wondering what strategies some of you in the forum may have used to widen the scope of the changes included/documented in your CM process.

Typically, the changes that are entered into our system are changes that will have some impact on service availability or have some operational requirements for implementation. Our sense is that there are a lot of undocumented changes that are implemented and our experience tells us that some of those changes do cause incidents.

We are thinking through a couple of strategies to get these changes into the process; such as beginning a standard change process, which would include abbreviated entry of data in the RFC (simplifying the process), the use of Service Catalogs and service requests (as opposed to email, phone) to drive work and therefore drive the changes. Either of these will take some time for adoption/implementation.

There are some large issues in managing/implementing either of those strategies and that's why I am wondering if there are others strategies or "lessons learned" in doing this.
Back to top
View user's profile

Joined: Feb 20, 2007
Posts: 14

PostPosted: Tue Feb 20, 2007 7:21 pm    Post subject: Reply with quote

perhaps I'm being simplistic, but I would say define what needs a change by the CI that is changed. if it changes one of these CIs in any way, it needs an RFC. Start with a critical set of CIs, then increase the scope.
The IT Skeptic
see you at
Back to top
View user's profile Visit poster's website
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

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.