Release management is the ITSM practice that plans, schedules, tests and makes new or changed services and features available to users in a controlled way. ITIL 4 puts its purpose simply: “to make new and changed services and features available for use.” In practice it links each release to approved changes, so IT knows what is going live, when, with what risk and how to back out. A typical release management process runs through six steps: plan, build, test, prepare, deploy and review.

What is release management?

A release is a set of new or changed components (software, configuration, hardware, documentation or process) that go live together. Release management decides what goes into each release, when it ships, who signs it off, and how users and support teams are prepared for it.

In ITIL 4, release management sits next to two related practices. Change enablement assesses and authorises changes. Deployment management physically moves components into live environments; ITIL 4 describes its purpose as “to move new or changed hardware, software” and other components, such as documentation and processes, into live environments. Release management is the coordinating layer between them: it bundles authorised changes into releases and makes sure the service is ready to use once deployment is done.

Without it, teams see the same symptoms again and again: versions that differ between environments, deployments nobody told the service desk about, changes that collide on the same weekend, and rollbacks that were never tested.

Release management vs change management vs deployment

The three are easy to blur, and many tools put them on one screen. This table shows who does what.

Change management (change enablement)Release managementDeployment management
Main questionShould we make this change, and when?What goes live together, and is the service ready?How do we move the components into live?
Unit of workChange request (RFC)Release (a bundle of one or more changes)Deployment to an environment
Key outputAuthorised change with risk assessmentRelease plan, readiness sign off, release notesComponents installed and verified
Typical ownerChange manager and CABRelease managerOperations, DevOps or platform team
ExampleApprove upgrading the HR system to version 9Bundle the version 9 upgrade with two fixes for the May releaseInstall version 9 on production servers on Saturday night

Why release management matters

  • Fewer failed releases. Testing gates and readiness checks catch issues before users do.
  • Lower risk. Every release carries a risk assessment and a rollback plan, so a bad release is reversed calmly instead of debugged live.
  • Control and audit. You know who approved what, which changes went into which release, and when. Auditors for ISO 20000 and similar standards ask for exactly this.
  • No surprise for the service desk. Support teams get release notes and known issues before go live, so they can answer the first calls.
  • Predictable delivery. A release calendar lets the business plan training, communications and freeze periods.

The release management process: 6 steps

  1. Plan the release. Agree the scope (which approved changes and features are in), the release type (major, minor or emergency), dates, environments and owners. Check the change calendar for collisions with other work and freeze periods. Example: the May release will include the HR system upgrade and two payroll fixes, ship on 18 May, and needs CAB approval by 9 May.
  2. Build and configure. Package the release: code, configuration, scripts, data migrations and documentation, each with a version number. Use the same build for every environment, so what you tested is exactly what you deploy.
  3. Test and accept. Run functional, regression, integration and performance tests, then user acceptance testing (UAT) with business users. Track each test cycle, its cases, results and open bugs per feature. A feature is not ready until its bugs are resolved or explicitly accepted.
  4. Prepare for deployment. Finalise the deployment plan, the rollback plan and the release notes. Get the go or no go decision from the release owner and, where your process requires it, the CAB. Brief the service desk and schedule user communications.
  5. Deploy. Move the release into production in the agreed window, using the approach that fits the risk: a big bang cutover, a phased rollout by site or user group, or a parallel run. Verify each step and keep the rollback trigger criteria in front of the team.
  6. Review and close. Watch incidents and performance for an agreed period after go live (early life support). Hold a short post implementation review: did the release meet its goals, what broke, what should change next time. Update the CMDB and close the linked change records.

Release readiness checklist

Use this before every go or no go meeting. If any line is a “no”, the release either waits or the risk is explicitly accepted and recorded.

CheckReady?
Scope is frozen and every item links to an approved changeYes / No
Release has a risk assessment and ratingYes / No
All test cycles complete; open bugs resolved or accepted in writingYes / No
UAT signed off by the business ownerYes / No
Deployment plan with named owners and timingsYes / No
Rollback plan written, with clear trigger criteriaYes / No
No collision on the change calendar; outside any freeze periodYes / No
Release notes and known issues shared with the service deskYes / No
User communication scheduledYes / No
Early life support cover and review date agreedYes / No

Key roles in release management

In a small team one person may hold several of these roles. What matters is that each responsibility has a named owner for every release.

RoleResponsibility
Release managerOwns the release plan and calendar, coordinates teams, runs go or no go
Change manager and CABAssess and authorise the changes inside the release
Product or service ownerSets scope and priorities, accepts business risk, signs off UAT
Quality or test managerPlans test cycles, tracks defects, confirms readiness
Deployment, operations or DevOps teamBuilds the pipeline, executes deployment and rollback
Service desk leadPrepares support teams, monitors incidents in early life support

Release management best practices

  • Link every release to approved changes. If a component is not covered by an authorised change, it does not ship. This is the single control that makes audits easy.
  • Release smaller and more often. Smaller releases are easier to test, explain and roll back. Batch work into a regular release train where the business allows.
  • Classify releases. Major, minor and emergency releases need different levels of approval and testing. Define them up front so emergency fixes do not bypass control by default.
  • Use one release calendar. Show releases, changes and freeze periods together so collisions are visible weeks ahead.
  • Always have a tested way back. A rollback plan that has never been rehearsed is a hope, not a plan.
  • Automate the repetitive parts. Automate builds, tests and deployment steps where you can, and automate the record keeping too: release registration, status updates and notifications.
  • Bring the service desk in early. Share release notes and known issues before go live, and track incidents linked to the release afterwards.
  • Measure and review. Track release success rate, rollback count, incidents caused by releases and schedule adherence, and review them each quarter.

Read how Leader IT, which serves clients in the Middle East, used Infraon ITSM to improve customer satisfaction and agent productivity by up to 75%.

Release management metrics

Report these per release and as a quarterly trend. Linking incidents to releases in your ITSM tool is what makes the third metric possible.

MetricWhat it tells you
Release success rateShare of releases deployed without rollback or major incident
Rollback frequencyHow often releases are reversed; a rising rate points to weak testing
Incidents caused by releasesIncidents linked to a release in its early life support window
Schedule adherenceReleases shipped in the planned window
Lead timeTime from change approval to release in production
Emergency release shareA high share suggests planning or testing gaps

Release management tools: what you need

Most organisations use two kinds of tools together. CI/CD pipeline tools automate building, testing and deploying code. An ITSM release management module governs the release: scope, approvals, risk, test sign off, schedule, communication and the audit trail, and links all of it to change, incident and the CMDB.

If you run infrastructure, packaged applications or vendor upgrades as well as in house software, the ITSM side matters most, because much of what you release never touches a code pipeline. When you compare tools, check for:

  • Release records created from approved changes, with the link kept both ways
  • Release risk assessment templates and ratings
  • Feature, task and test cycle tracking, including UAT, inside the release
  • Release and deployment models you can version and reuse
  • A change calendar that detects collisions
  • CMDB integration, so CIs update when the release completes
  • Notifications and escalation when a release slips past its tolerance
  • Deployment options that meet your compliance needs (SaaS or on premise)

Release management in Infraon ITSM

Release management is part of the Infraon ITSM Professional plan ($57 per user per month), alongside change management with CAB and problem management. It covers the governance side of the process above:

  • Release records from changes. Create a release record from any change record and keep releases linked to their changes, contracts and CIs in the CMDB.
  • Risk and rollback. Release risk templates, risk assessment, results and rating, with the rollback plan held on the release.
  • Features and test cycles. Define release features with an owner, due date and tasks, and record test cycles, test cases, results, bugs and UAT cases for each feature; all must be resolved before the feature closes.
  • Release and deployment models. Define, version and reuse structured release and deployment models and templates; bundle and schedule release packages and track distribution and installation.
  • Planning and collaboration. Plan releases with the teams involved, and automate release and deployment meetings, schedules and activity updates. Release registration and status updates are automated through the release lifecycle.
  • Change control around it. CAB workbench for scheduling CAB meetings, a change calendar that detects collisions, and CMDB protection so CIs are not updated when a change fails.
  • Alerts. Email and SMS notifications and escalation when a release breaches its tolerances.

Infraon ITSM runs as SaaS, or as the Enterprise edition on premise or hybrid in the country you need, with Arabic language support. It holds ISO/IEC 27001:2022, ISO 20000-1:2018 and SOC 2 Type 2, and is PinkVERIFY verified for 12 ITIL processes.

See release records, risk templates and test cycle tracking on the Infraon release management page.

Frequently Asked Questions

What is release management in ITSM?

It is the practice of planning, scheduling, testing and making new or changed services and features available to users in a controlled way, with each release linked to approved changes.

What are the steps in the release management process?

A typical process has six steps: plan the release, build and configure, test and accept, prepare for deployment, deploy, and review and close.

What is the difference between release management and change management?

Change management decides whether a change should happen and authorises it after a risk assessment. Release management bundles authorised changes into releases, plans and tests them, and makes sure the service is ready when they go live.

What is the difference between release management and deployment management?

In ITIL 4, deployment management moves components into live environments. Release management decides what goes into a release and makes the new or changed service available for use. Deployment is one step inside the wider release.

Who is responsible for release management?

A release manager owns the release plan and calendar and runs the go or no go decision, working with the change manager and CAB, the service owner, the test manager, the deployment team and the service desk.

How do you measure release management success?

Track release success rate, rollback frequency, incidents caused by releases, schedule adherence, lead time from approval to production and the share of emergency releases.

Do I need a separate release management tool if I use CI/CD?

CI/CD tools automate builds and deployments. You still need release governance: scope, approvals, risk, UAT sign off, schedules and audit records linked to change and incident. Many teams keep that in their ITSM tool and connect it to the pipeline.

Release management is in Infraon ITSM Professional at $57 per user per month; save 20% with yearly billing. Start a 14 day free trial or see all plans.

Do you like PRAVEEN SINHA's articles? Follow on social!
Start Free Trial