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: VaughnBe
New Today: 8
New Yesterday: 34
Overall: 231580

People Online:
Visitors: 127
Members: 0
Total: 127



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 - Change the term Standard change to something else
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Change the term Standard change to something else

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

Joined: Nov 27, 2012
Posts: 1

PostPosted: Wed Nov 28, 2012 7:35 am    Post subject: Change the term Standard change to something else Reply with quote

An environment I'm the change manager for is folding in new Change Management processes, ITIL and best practices in other areas such as incident.

Now, there is a discomfort with the term "Standard" change. There is a push to call this "Routine" instead. There is no push to change the associated definition, just the word.

Now, I'm against this. The reason is that the current environment has some miles on it and most terms used are currently not in alignment with ITIL/Best Practices.

Seems to me that even if the term "Standard" means different things to different people now, you have to put a stake in the ground. As a matter of fact some seminars regarding ITIL have been provided to let folks get used to ITIL, it's suggestions and terms.

So, am I being petty and concerned with nothing or am I on the right path? If this terminology swap goes forward, similar name changes will likely permeate new ITSM tool(s) that are currently being deployed (since we all know these tools are all editable/customizable).

Back to top
View user's profile
Senior Itiler

Joined: Sep 16, 2006
Posts: 3597
Location: London, UK

PostPosted: Wed Nov 28, 2012 4:43 pm    Post subject: Reply with quote

Oh the horror.. oh the inhumanity

Thank the gods that you prevented this from happening..

Imagine the scene when the ITIL Police comes in like the SPanish Inquistion and hangs the miscreants by their mouse cable,


Wait.. there is no ITIL Police...


Take the following sentence to heart


You can call Standard CHanges - Bananas. No one cares but your own organization
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile
Senior Itiler

Joined: Mar 04, 2008
Posts: 1894
Location: Helensburgh

PostPosted: Thu Nov 29, 2012 2:20 am    Post subject: Reply with quote

I have never liked the term standard change, because a) it encourages a lack of definition for all of its instances; b) it tends to narrow the scope of things that can (and should) get such special treatment (especially by applying it mostly to simple things; c) it is defined in almost as many ways as there are organizations using the term.

The first two reasons apply to your organization's proposed renaming - in spades for the second reason.

The only part of the concept that has much value is the idea that some kinds of predictable changes can be treated differently in ways that are more efficient and often quicker than going through the default change process. Such changes need to have a documented procedure of their own which covers how to achieve the correct governance for them, what conditions must apply for any change to qualify for this treatment and how scheduling will be managed.
"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

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.