ITIL 4 Deployment Management flashcards
ITIL 4 Deployment Management · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Deployment management
- The practice of moving new or changed hardware, software, documentation, processes, or other components to live environments, and may also deploy components to other environments for testing or staging.
- Release management
- The practice of making new and changed services and features available for use, distinct from deployment management, which focuses on moving components into environments.
- Big bang deployment
- A deployment approach in which all components are deployed at once to all users or environments, typically used when phased or continuous approaches are not feasible.
- Phased deployment
- A deployment approach that introduces changes incrementally, for example by user group, location, or component, reducing risk and allowing early feedback.
- Continuous deployment
- A deployment approach in which changes are deployed frequently and automatically through a pipeline, often many times per day, with strong automation and testing.
- Pull deployment
- A deployment approach in which the user or consumer initiates the deployment or update at a time convenient to them, rather than the provider pushing it.
- Target environment
- The specific environment, such as development, test, staging, or production, into which components are deployed and where they must function correctly.
- Deployment planning
- The activity of defining scope, schedule, dependencies, rollback approach, resources, and acceptance criteria before any component is moved to the target environment.
- Pre-deployment checks
- Verification activities performed before deployment, including environment readiness, capacity, configuration baselines, dependency availability, and change authorization status.
- Post-deployment verification
- Confirmation after deployment that components are installed, configured, and functioning according to acceptance criteria, with rollback or remediation triggered on failure.
- Rollback plan
- A predefined set of triggers, steps, and responsibilities for restoring the prior state if a deployment fails or does not meet acceptance criteria.
- Deployment record
- A record capturing what was deployed, where, when, by whom, and the outcome, linked to change and configuration records for traceability and audit.
- Deployment manager
- The role responsible for planning, coordinating, and overseeing deployment activities, ensuring they meet requirements and are properly authorized and verified.
- Deployment engineer
- The role that executes deployment activities, including installation, configuration, verification, and rollback, often using automation tools and defined procedures.
- Centralized deployment team
- An organizational structure in which a dedicated team performs deployments for the whole organization, providing consistency and specialized expertise.
- Decentralized deployment
- An organizational structure in which deployment responsibilities are embedded within product or value stream teams, supporting speed and autonomy.
- Deployment competency
- The knowledge and skills required for deployment, including environment and infrastructure knowledge, automation, configuration management, and change control awareness.
- RACI for deployment
- A responsibility model clarifying who is responsible, accountable, consulted, and informed for each deployment activity, reducing ambiguity and conflict.
- Configuration management database
- A database that stores configuration records and their relationships, used by deployment management to track components and their dependencies in environments.
- CI/CD pipeline
- An automated toolchain that builds, tests, and deploys changes, enabling repeatable and consistent deployments with reduced manual error.
- Infrastructure as code
- A practice of managing and provisioning infrastructure through machine-readable definition files, supporting consistent and repeatable deployments.
- Environment baseline
- A documented and controlled configuration of an environment against which drift can be detected and corrected after deployment.
- Deployment automation
- The use of tools and scripts to perform deployment activities, reducing manual error and improving repeatability, consistency, and speed.
- Deployment logging
- The capture of deployment events and outcomes in logs, supporting audit, troubleshooting, verification, and continual improvement of deployment quality.
- Supplier deployment services
- Deployment activities performed by external providers, governed by contracts and SLAs that specify scope, quality, and handover requirements.
- Shared responsibility model
- A model clarifying which deployment and security tasks belong to the service provider and which belong to the consumer, common in cloud services.
- SIAM in deployment
- Service integration and management approaches that coordinate multiple suppliers involved in deployment activities, ensuring consistent delivery and accountability.
- Deployment success rate
- A metric measuring the percentage of deployments that complete without failure or rollback, indicating deployment quality and process effectiveness.
- Deployment frequency
- A metric measuring how often deployments occur, reflecting the speed and agility of the deployment process and value stream.
- Change failure rate
- A metric measuring the percentage of changes that result in failure or require remediation, indicating deployment and change quality.
- Lead time for changes
- A metric measuring the time from change initiation to deployment in the target environment, reflecting deployment efficiency and value stream flow.
- Value stream mapping
- A technique for visualizing the flow of work through the deployment process, identifying delays, handoffs, and bottlenecks that increase lead time.