|
|
- Goal
- To take an holistic view of a change to an
IT service and ensure that all aspects or a
release, both technical and non-technical are
considered together
- Why release management
- Large or critical hardware roll-outs
- Major software roll-outs
- Bundling or batching related sets of changes
- Responsibilities
- Planning and overseeing the successful
roll-out of new and changed software and
associated hardware and documentation
- Liaison with
change management to agree the exact content
and roll-out plan for the release
- Ensuring that all items being rolled out or
changed and secure and traceable via the CMDB
- Managing customers and users expectations of
releases and roll-outs.
- Types of release
- Full release: all components of the release
are built, tested, distributed and implemented
together
- Delta release: only those CIs that have
actually changes since the last release are
included
- Package release: individual releases, both
full and delta are grouped together to form a
package for release
- DSL (Definitive Software Library)
- Contains the master copies of all controlled
software in an organisation, including purchased
software as well as software developed on-site
 |
|
|
|
|
|
|
|