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
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.
Joined: Jan 23, 2006 Posts: 13 Location: San Francisco, CA
Posted: Wed Oct 11, 2006 3:53 am Post subject: Release Management Deployment
Hi,
We are currently implementing release management in our company. Do most companies set up the release management process to control the move from dev to test to stage to prodcution or just the deployement to prodcution?
Also, do all applicaitons go through an enterprise wide release or just critical, large, SOX, etc. applications? Smaller applications would still follow the process, but just get deployed at a system/application level rather than the "big" release?
I do not know what is the common practice, but the best practice (that's ITIL) is to have them all under Release Management IF THIS IS CONVENIENT for your organization.
Nothing forbids from having the development team do whatever they like (without following any process) during the development, testing and staging and deliver a tested version to be deployed under Release Management.
Joined: Jan 16, 2005 Posts: 37 Location: New Zealand
Posted: Tue Oct 17, 2006 1:15 pm Post subject:
You have to consider carefully the size of your organisation against the objectives that you are trying to achieve with the implementation of a Release Management process.
From my perspective, you need to determine the scope of your Release Management. I.e. Should all applications and infrastructure be subject to Release Management? Or perhaps only critical systems and infrastructure? Once you've established that, all changes to those services will be subject to Release Managament, regardless of size... even the smallest change could ripple into something bigger if not developed and tested properly.
Determining how you Release changes into production is also important to consider. The advantage of a good Release Management process is that you can package the Changes into a single Release, thereby minimising unavailability of the service affected by the Change.
A good Release Management process is vital where you have a SOA environment as the dependencies between applications and infrastructure are often blurred and many different parts of the organisation could be affected if you get it wrong.
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