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: MMontanez
New Today: 0
New Yesterday: 48
Overall: 146028

People Online:
Visitors: 55
Members: 0
Total: 55

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 - CSF's for Change and Release Management
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

CSF's for Change and Release Management

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


Joined: Mar 13, 2006
Posts: 1

PostPosted: Mon Mar 13, 2006 10:20 pm    Post subject: CSF's for Change and Release Management Reply with quote

I've been tasked with drawing up some Critical Success Factors for Change and Release Management and I'm reaching a bit of an impassse!

Has anyone else got a view on what should be included? I'm starting from a blank canvass!
Back to top
View user's profile
rjp
Senior Itiler


Joined: Mar 12, 2005
Posts: 255
Location: Melbourne, Australia

PostPosted: Mon Mar 13, 2006 11:01 pm    Post subject: Reply with quote

Just quickly - the following should get you started Smile

From the ITIL,

Change Management CSFs

  • a repeatable process for making Changes
  • make Changes quickly and accurately (business driven needs)
  • protect services when making Changes
  • deliver process efficiency and effectiveness benefits.


Release Managemnt CSFs

  • better quality software and hardware
  • a repeatable process for rolling out software and hardware Releases
  • implementation of Releases swiftly (business driven needs) and accurately
    cost-effective releases.


From BS15000-1 the following might also help

change Management


  • Service and infrastructure changes shall have a clearly defined and documented scope.
  • All requests for change shall be recorded and classified, e.g. urgent, emergency, major, minor.
  • Requests for changes shall be assessed for their risk, impact and business benefit.
  • The change management process shall include the manner in which the change shall be reversed or remedied if unsuccessful.
  • Changes shall be approved and then checked, and shall be implemented in a controlled manner.
  • All changes shall be reviewed for success and any actions taken after implementation.
  • There shall be policies and procedures to control the authorization and implementation of emergency changes.
  • The scheduled implementation dates of changes shall be used as the basis for change and release scheduling.
  • A forward schedule of change shall be maintained and communicated to relevant parties.
  • Change records shall be analysed regularly to detect increasing levels of changes, frequently recurring types, emerging trends and other relevant information.
  • The results and conclusions drawn from change analysis shall be recorded.
  • Actions for improvement identified from change management shall be recorded and input into the service improvement plan.


Release Managment

  • The release policy stating the frequency and type of releases shall be documented and agreed.
  • The service provider shall plan with the business the release of services, systems, software and hardware.
  • Plans on how to roll out the release shall be agreed and authorized by all relevant parties, e.g. customers, users, operations and support staff.
  • The process shall include the manner in which the release shall be
    backed-out or remedied if unsuccessful.
  • Plans shall record the release dates and deliverables and refer to related change requests, known errors and problems. They shall be communicated to incident management.
  • Requests for change shall be assessed for their impact on release plans.
  • Release management procedures shall include the updating and changing of configuration information and change records.
  • Emergency releases shall be managed according to a defined process that interfaces to the emergency change management process.
  • A controlled acceptance test environment shall be established to build and test all releases prior to distribution.
  • Release and distribution shall be designed and implemented so that the integrity of hardware and software is maintained during installation, handling, packaging and delivery.
  • Success and failure of releases shall be measured.
  • Measurements shall include incidents related to a release in the period following a release.
  • Analysis shall include assessment of the impact on the business,
  • IT operations and support staff resources, and shall provide input to the service improvement plan.


If you formulate a list of say the top five most important objectives for your implementation, from the above, you should get a workable set of CSFs. (Remember they are relative to the maturity level you are aiming for.)
Back to top
View user's profile Send e-mail AIM Address Yahoo Messenger
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.