Home 
 1. Overview  
 What is Release Management?  
 How Release Management works  
 What does Release Management cost?  
 2. Implementation guide  
 Define what needs to be done  
 Prepare to implement  
 Implement (TT5293) 
 Review the implementation  
 Implementation resources  
 3. Operations guide  
 What needs to be done?  
 When does it need doing?  
 Who does it?  
 Operational resources  
 4. Toolkit  
 Examples  
 Templates  
 5. Roles and responsibilities  
 Release manager  
 Build developer  
 Acceptance tester  
 Installer  
 6. Review of Release Management (F070207) 
 Recap of Release Management  
 Checklist  
Recap of Release Management
Release Management summary What you should expect What you should have achieved Benefits of having implemented
In release management we introduced the process of planning, building, testing and deploying ICT equipment, and managing software and software licences. We gave you an overview of the whole Release Management process and an implementation guide giving step-by-step instructions to help you implement a release management process that we believe is appropriate for the needs of schools. An operations guide gave you a list of ongoing activities required by the process in order for you to keep it going and reap the benefits. We described roles and responsibilities and offered guidance on how to assign roles. We removed anything non-essential to give you a lean process requiring the minimum of effort and resource.

Check your understanding of the process by following:
Release Management summary
Step
Tasks
Create a definitive software library.
Create a secure, central storage area for all software including:
  • original software
  • copies of software used for installation purposes.
Keep a log of software licences and a record of which computers they have been assigned to.
Create standard builds for all hardware and software services.
Create a procedure document for each different service, including:
  • design details - the components that make up the service
  • installation details - the steps required to install the service correctly
  • stability test details - details of the environment the new service must work within without harming it
  • acceptance test details - functionality test criteria to ensure that the new service works correctly.
Make standard builds available to technical staff for installation as required.
Ensure that build instructions and the correct version of software are used for subsequent installations by:
  • storing the build software in the definitive software library
  • storing the build procedure in the configuration management database (CMDB)
  • informing all technical staff of the release.
Use standard builds for all new installations.
Use the installation checklist for every new hardware or software installation to ensure that:
  • staff take all of the appropriate steps and do not accidentally forget anything
  • end-user details are captured.
Ensure that new types of service go through the Release Management process before being installed.
Implement other FITS processes to draw attention to new requirements:
  • the incident/request process for new end-user requirements
  • the change management process for new infrastructure requirements.

What you should expect
What you should expect now that you have implemented Release Management
  • Technical support staff document all software and hardware installations.
  • Technical support staff use build procedures and install checklists to install new equipment.
  • End-users do not install their own hardware or software.
  • No one installs software if no licence is available.
  • The correct versions of software are always installed.
  • Software and hardware services are stable.
  • All new types of hardware and software are put through the Release Management process before they are deployed.
What you should have achieved
What you should have achieved through Release Management
  • You have a release policy describing the frequency and nature of upgrades.
  • You receive fewer ad hoc requests for new hardware or software.
  • All hardware and software installations have been tested and documented.
  • Hardware and software is installed consistently each time.
  • You spend less time resolving incidents and problems caused by badly installed hardware and software.
  • All software is stored centrally.
  • You can tell which version of software is the correct and current version.
  • You have a list of all software licences.
  • You know to whom or what each software licence is assigned.
Benefits of having implemented
Benefits of having implemented Release Management
  • Planning for future releases is more efficient as a result of having a release policy.
  • You handle changes to software more efficiently by bundling them together.
  • End-users suffer less frequent disruption caused by changes.
  • Having a repeatable process for installations is quicker and less error prone than relying on memory.
  • Installing equipment in the same way each time makes support easier because you have to resolve incidents and problems only once.
  • Emphasis on training before rollout means that users can make the most of new functionality as soon as it is available.
  • Software version control ensures that no one reintroduces problems through installing the wrong version.
  • New technical staff can follow documented instructions created by predecessors so continuity of skills is preserved.
  • Technical staff unfamiliar with particular software or hardware have documented guidance which can help their personal development.
  • Resolution of incidents is quicker through fast reinstallation of builds.
  • Quicker resolution of problems is possible through comparison with standard build instructions.
  • Less time spent on incidents and problems means more time available for proactive support.
Top