I85PREP
⌘ K
ITIL 4 Release Management study materials
ITIL 4 Release Management study resources

ITIL 4 Release Management cheat sheet

ITIL 4 Release Management · Keep the key ideas within reach.

Quick reference

ITIL 4 Release Management

  • Release management makes new and changed services and features available for use; it is a practice in the ITIL 4 service value chain, distinct from deployment management, which moves components into live environments.

  • ITIL 4 defines three release types: phased release (functionality to a subset of users first, then expanded), continuous delivery (small increments delivered frequently, often feature-flagged), and big bang release (all components to all users at once).

  • Release management focuses on the release itself (the collective set of components made available together) and its acceptance criteria; deployment management focuses on the technical transfer, build, and installation of components.

  • The release management practice includes four activities: release planning, release design and build, release testing and acceptance, and release closure (post-implementation review and lessons learned).

  • Release planning defines scope, schedule, resources, risk, and the release policy; it aligns with change enablement (change authorization) and service validation and testing (verification before release).

  • A release unit is the set of components released together; its granularity is chosen by balancing frequency of change, impact of failure, and the cost/complexity of packaging and testing.

  • Release acceptance criteria must be agreed and documented before release; they typically cover functional tests, non-functional tests (performance, security), and user acceptance, with sign-off by the service owner or authorized change authority.

  • Rollback and remediation plans are mandatory design elements: define the trigger conditions, the maximum tolerable downtime, and the verified procedure to restore the prior known-good state before authorizing a release.

  • Release records, version identifiers, and configuration data in the configuration management database (CMDB) must be updated at release closure so that the current state of the live environment is accurate and auditable.