Service Transition, Change and Release Management
This domain tests the controlled movement of services into live use. Expect transition planning, change enablement, release and deployment, service validation and testing, knowledge management and service asset and configuration management.
Core rules and concepts
- Transition planning coordinates resources, roles, schedules and acceptance criteria so that a service is ready for operation.
- Change enablement maximizes successful changes by assessing risk and authorizing work. Common change types are standard, normal and emergency.
- Standard changes are pre-authorized, low-risk and repeatable. Normal changes follow assessment and approval. Emergency changes use an expedited path with retrospective review.
- Release makes a version available for use. Deployment moves it into the live environment. They are related but not identical.
- Configuration management identifies configuration items, records relationships and maintains baselines in a configuration management system.
Worked example
A database schema change must be applied to a live payment service. The team classifies it as normal because it is not pre-authorized and has rollback complexity. They assess impact and risk, define a tested backout plan, obtain change authority approval, schedule a release window, deploy to staging, validate, then deploy live. After verification they update the CMDB and record lessons. The reasoning is that the change model chosen must match risk, and release, deployment and validation are separate controlled steps.
Traps
Using 'release' and 'deployment' interchangeably; letting emergency changes skip all documentation; populating a CMDB but never maintaining it; judging change success only by volume; testing only the happy path.