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.
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.
Search
Languages
Select Interface Language:
Advertising
Please contact us via the feedback page to discuss advertising rates.
Posted: Thu Aug 02, 2007 7:12 pm Post subject: Changes v's Releases
Hi All,
I’m looking at making some improvements in my current Change Management process and part of this will review the relationship with Release Management and specifically what constitutes a Change versus what constitutes a Release.
I would love to know how other organisations make the differentiation, how do you decide what’s a change and what’s a release and how do you manage the relationship between the two.
Joined: Jan 01, 2006 Posts: 500 Location: New Jersey
Posted: Sat Aug 04, 2007 11:39 am Post subject:
Hi Ed,
Ed wrote:
A Change is a Request For any alteration to any service, hardware, software, etc. etc. hence RFC - Request For Change
A Release is what puts that Change into the Live environment after risk assessment, testing, and authorisation.
To add to this, a Release can be composed of one or more Changes. For example, a Software Product Release may implement N different Requests for Change.
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