ITIL Foundation Online Training - $47/mo Description: 14+ Hours, 200+ Practice Questions, Lifetime Access, 100% Online, Self-paced Click Here

10 Full ITIL Mock Exams for only $25/mo.Check if you are ready to take the ITIL Exam and crack it in the first attempt Click Here

Wednesday, March 14, 2012

More on Release and Deployment Management

Before we go any further with Release & Deployment Management, we first need to understand their definitions.
A Release is a collection of hardware, software, documents, processes or other components required to implement one or more approved Changes to IT services. The contents of each Release are managed, tested and deployed as a single entity.
Deployment is the activity responsible for the movement of new or changed hardware, software, documentation, process etc. to the Live Environment.

A Release Unit:

A Release Unit typically includes sufficient components to perform a useful function. For example, one Release Unit might be a desktop PC, including hardware, software, licences, documentation etc. There might be standardized units for different roles or departments, or the desktop might be customised for each new recruit (where each instance is a separate Release Unit). Another Release Unit might be a complete application, including IT Operations procedures and user training.

It is possible that a Release will consist of more than one Release Unit. A Release Package is one or more Release Units that are required to implement a new or changed service.

Release Policy:

A Release Policy should be defined as part of the management control over releases. In fact, it is unlikely that an organization will have a single Release Policy; it is more likely to have several, each covering one or more services. Each Policy should cover Identification, Roles and Responsibilities, expected frequency, change acceptance criteria, automation, configuration verification, entry and exit criteria through phases, and handover from Early Life Support to Operations.

Prev: Goals, Purpose and Objectives of Release & Deployment Management

Next: Basic Steps in Release & Deployment Process


  1. Please elaborate why we need Release Management System? Instead we can use change management system itself?
    What is the difference between those?

    1. Sivanantham - A change management system is used to manage changes to an existing system. As a result of implementing the change, the development team will be making code changes and then these code changes have to be implemented in the production system. The release management system takes care of this.

      A change management system will track all the changes, prioritize them and only approve those that have formal documentation and business justifications.

      A release management system will track all the code changes that have happened to the system and will ensure that these changes get released to production properly.

      Change management system results in code changes and the release management system releases/deploys these code changes into production

      Hope this clarifies.



© 2013 by All rights reserved. No part of this blog or its contents may be reproduced or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission of the Author.


Popular Posts