Systems, configurations, and IT infrastructures are subject to constant change. This, in return, can lead to problems in applications and business processes that can't always be anticipated. Consequently, release management is meant to minimize the risk of business process interruptions associated with configuration changes.
These interruptions have a variety of root causes. Most of the time, however, they are brought about by poorly planned or insufficiently tested system configurations.
This makes careful release planning imperative – in no small part because of cost considerations.
Full-fledged release management covers the following:
- determine the functional scope
- meticulously schedule the release approval process in agreement with change and/or product management processes
- implement quality assurance to monitor compliance with the criteria that were established for the creation of a release as part of the change and/or product management process
- document scope and changes
- manage version histories


