ITIL 4 Deployment Management cheat sheet

Deployment management moves new or changed hardware, software, documentation, processes, or any other component to live environments; it may also deploy components to other environments for testing or staging.

Core purpose: make the change available for use by ensuring components are correctly assembled, installed, configured, and handed over in the target environment.

Deployment management is one of the ITIL 4 technical management practices; it is not the same as release management, which makes services available to users.

Scope spans all environments (development, test, staging, production) and all component types, including infrastructure, applications, middleware, and configuration items.

A deployment can be performed without a release (e.g., components deployed to a test environment); a release usually involves one or more deployments.

Deployment approaches: big bang (all at once), phased (incremental by user group or component), continuous (frequent small deployments), and pull (user-initiated).

Deployment management is responsible for the technical 'how' of moving components; change enablement authorizes the change, and release management controls availability to users.

Key distinction: deployment focuses on the target environment and technical installation; release focuses on making the service available and usable by consumers.

Typical deployment activities in sequence: plan, design/approach selection, build and test, prepare target environment, deploy, verify, hand over, and close.

Deployment planning defines scope, schedule, dependencies, rollback approach, resources, and acceptance criteria before any component is moved.

Pre-deployment checks include environment readiness, capacity, configuration baselines, dependency availability, and change authorization status.

Deployment execution should follow defined procedures and use automation where feasible to reduce error and improve repeatability.

Post-deployment verification confirms components are installed, configured, and functioning per acceptance criteria; failed verification triggers rollback or remediation.

Rollback or back-out plans must be defined before deployment; they specify triggers, steps, and responsibilities for restoring the prior state.

Deployment records should be linked to the change record, configuration items, and release record to maintain traceability.

Deployment management interacts with service validation and testing, change enablement, release management, and configuration management.

Typical roles: deployment manager (plans and coordinates deployments), deployment engineer/technician (executes), and release manager (coordinates releases).

Deployment roles may be centralized (a dedicated team) or decentralized (embedded in product teams); ITIL 4 favors flexible, value-stream-aligned structures.

Competencies include environment and infrastructure knowledge, automation and scripting skills, configuration management expertise, and change control awareness.

Deployment personnel need strong attention to detail, verification discipline, and the ability to follow defined procedures under time pressure.

Collaboration with development, operations, testing, and security teams is essential; deployment is a shared responsibility across the value stream.

RACI or similar responsibility models clarify who approves, executes, verifies, and is informed for each deployment activity.

Organizational structures should support fast feedback and continuous deployment where the service requires it, while retaining control for high-risk changes.

Deployment management relies on configuration management databases (CMDB) and configuration management systems to track components and their relationships.

Deployment tools include CI/CD pipelines, configuration management tools (e.g., infrastructure-as-code), and orchestration platforms.

Deployment records capture what was deployed, where, when, by whom, and the outcome; they support audit, troubleshooting, and continual improvement.

Automation reduces manual error and enables repeatable, consistent deployments; it should be tested and version-controlled like other components.

Environment inventories and baselines are key information assets; drift from baselines should be detected and corrected.

Monitoring and logging tools provide post-deployment verification data and feed back into deployment quality metrics.

Access controls and segregation of duties protect production environments; deployment credentials should be managed securely.

Integration between deployment tools, change management systems, and CMDB ensures traceability and informed decision-making.

Deployment may involve suppliers providing infrastructure (cloud providers), software, tooling, or deployment services; their responsibilities must be defined in agreements.

Service integration and management (SIAM) approaches help coordinate multiple suppliers involved in deployment activities.

Supplier-provided deployment services should be governed by clear SLAs, OLAs, and contracts specifying scope, quality, and handover requirements.

When suppliers deploy components, the organization retains accountability for verifying that deployment meets its requirements.

Shared responsibility models (e.g., in cloud services) clarify which deployment tasks belong to the provider and which to the consumer.

Supplier performance should be monitored and reviewed as part of value stream and continual improvement activities.

Partner and supplier relationships should be managed through the supplier management practice, with deployment-specific requirements captured explicitly.

Deployment management contributes to the value stream by moving components into environments so that services can be released and consumed.

Key metrics: deployment success rate, deployment frequency, lead time for changes, mean time to restore (MTTR), and change failure rate.

Deployment quality metrics include rollback rate, post-deployment defect rate, and verification pass rate.

Deployment efficiency metrics include deployment duration, resource utilization, and degree of automation.

Continual improvement uses deployment data to identify recurring failures, bottlenecks, and automation opportunities.

Value stream mapping can reveal delays and handoffs in the deployment process that increase lead time.

Feedback loops from monitoring, incident management, and problem management inform improvements to deployment procedures and tooling.

Improvement initiatives should be prioritized by impact on service quality, risk reduction, and customer value.

Deployment management must align with change enablement to ensure changes are authorized before deployment.

Deployment management supports release management by making components available in the target environment for release.

Deployment management is closely linked to service configuration management, which maintains accurate records of deployed components.

Deployment management should consider security, compliance, and regulatory requirements for each environment.

Deployment management should support both planned and emergency deployments, with appropriate controls for each.

Deployment management should be integrated with incident and problem management to learn from deployment-related failures.

Deployment management should be continuously improved through measurement, feedback, and automation.