ITIL Release and Deployment Management: Strategies, Pipelines and Rollback

Building a new feature is only half the story; getting it safely into the hands of users is the other half. ITIL 4 separates two related practices. Release management makes new and changed services and features available for use. Deployment management moves new or changed hardware, software, documentation, processes or any other component to live environments. Understanding the difference helps you plan modern, frequent delivery without losing control.

Release vs Deployment

DeploymentRelease
MeaningMoving a component to an environmentMaking a feature or service available to users
ConcernTechnical: is the code in production?Business: can users now use it?
Who decidesEngineering and operationsProduct owner or service owner, with the business
ExampleNew version installed on servers, switched off for usersFeature turned on for all customers on Monday

The two can happen together or be separated. Teams that deploy code daily but release features on a business schedule use feature flags to keep the two apart.

Release Types

  • Big bang: everything is released at once to all users. Simple to describe but risky.
  • Phased: released in stages to groups of users, sites or regions.
  • Continuous: small changes flow to production automatically after passing tests.

Deployment Strategies

StrategyHow it worksBenefitTrade-off
RollingReplace instances one by oneNo full outageTwo versions run together for a time
Blue-greenRun old (blue) and new (green) environments, then switch trafficInstant rollback by switching backNeeds duplicate infrastructure
CanarySend a small share of users to the new version firstProblems affect few usersNeeds good monitoring and routing
Feature flagDeploy code switched off, then enable for chosen usersSeparates deployment from releaseNeeds flag management and clean-up

The Role of CI/CD

Continuous integration merges and tests code frequently; continuous delivery keeps it always ready to deploy; continuous deployment pushes every passing change to production automatically. A pipeline automates build, test, security checks and deployment, giving a consistent, repeatable route. This is the “optimize and automate” principle (see ITIL Guiding Principles) at work. The pipeline also provides evidence for change enablement: if each stage passes, risk is lower and many releases can be treated as standard changes (see Change Enablement).

Release Planning Checklist

  • Scope: what is included, and what is not.
  • Testing complete, with known defects reviewed and accepted.
  • Environment and data ready, with configuration checked.
  • Rollback or roll-forward plan written and, if possible, rehearsed.
  • Communication to users and support teams, with timing.
  • Support trained and knowledge articles ready.
  • Monitoring in place to detect problems quickly.
  • Go or no-go decision recorded, with named decision-makers.

Rollback and Roll-Forward

Rollback returns to the previous version. It is simple when only code changes but difficult when the database structure or data changes irreversibly. Roll-forward fixes the problem with a new release instead. Decide in advance which route you will use and the conditions that trigger it, for example “error rate above 2% for ten minutes”.

Worked Example

A bank plans to release a new payment screen. The team deploys the new code on Tuesday with the feature flag off and verifies it in production with test accounts. On Thursday, they enable it for 5% of customers (canary) and monitor errors and complaints. After a day with normal results, they raise it to 25%, then 100% on Monday. A bug found at 25% affects only the tablet layout; they switch the flag off for tablets, fix it and re-enable. No outage occurs, and the change record shows every step.

Common Mistakes

  • Treating deployment and release as the same thing.
  • Releasing on a Friday evening with no one on call.
  • Having no tested rollback or roll-forward plan.
  • Leaving old feature flags in the code indefinitely.
  • Not telling the service desk about a release until users call.
Key takeaways
  • Deployment moves components to environments; release makes features available to users.
  • Strategies such as blue-green, canary and feature flags reduce risk.
  • CI/CD pipelines give consistent, evidence-rich delivery that supports change enablement.
  • Plan rollback or roll-forward, monitoring and support readiness before every release.

Related Lessons