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: LorenzaOfs
New Today: 33
New Yesterday: 63
Overall: 149707

People Online:
Visitors: 70
Members: 1
Total: 71 .

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 - Standard Changes - When is an RFC Actually Required
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Standard Changes - When is an RFC Actually Required

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


Joined: Jun 02, 2009
Posts: 4
Location: Indianapolis, IN

PostPosted: Sat Jul 17, 2010 3:05 am    Post subject: Standard Changes - When is an RFC Actually Required Reply with quote

When is an RFC required for a Standard Change?
Back to top
View user's profile
Diarmid
Senior Itiler


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

PostPosted: Sun Jul 18, 2010 6:32 pm    Post subject: Reply with quote

That is entirely up to you.

In my opinion it is risky to perform any change without first asking permission. Whether you call this an RFC or something else is probably moot (except in the context of software-driven change management when it will depend on what your software permits you to do - I'm trying to be ironic here).

If you formally adopt a concept of "standard change" then you will define how to proceed with standard changes. I like the idea of having each standard change controlled by its own procedure which will define for that particular change what the change management requirements are and how change management should be effected, including authority, testing and scheduling (off the top of my head).
_________________
"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
Curtis_Rowell
Newbie
Newbie


Joined: Nov 19, 2010
Posts: 1

PostPosted: Wed Dec 15, 2010 2:03 am    Post subject: Re: Standard Changes - When is an RFC Actually Required Reply with quote

rlmx wrote:
When is an RFC required for a Standard Change?


An RFC should ALWAYS be required for a Standard or Assumed Approved change. However, the approval process is different for such a change because the risk level is low or nearly non-existent. But it is still a change and as such, should be documented.
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 Dec 15, 2010 7:10 pm    Post subject: Reply with quote

At the risk of being misunderstood, I would suggest that "standard changes" do not necessarily have "low or nearly non-existent" risks. What each one does have is a clearly defined consistent context that is safely manageable by a repeatable process which can then be predefined.

Something is safe to do because it is well understood and well controlled both technically and managerially. Few things are genuinely low-risk unless they are done "properly". Patching is often cited as a candidate for being a "standard change", but an injudicious patch application can be disastrous. Patching is not low-risk.
_________________
"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
SubbuA
Itiler


Joined: Jan 28, 2010
Posts: 33

PostPosted: Sun Jan 02, 2011 7:23 am    Post subject: When is RFC required for standard change???? Reply with quote

Please check if your organization has defined a process for handling standard change... If yes, there should a policy written on how to raise a standard change....

if there is no process defined, we can write one - but that is a job and not to be done for free

Regards,
Subbu A
_________________
Regards,
Subbu A
ITIL Certified and well experienced
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.