A practical, self-paced course for IT teams that need changes to be both safe and fast. Six lessons cover the purpose of change enablement, change types and risk assessment, how to set up change authority without a bottleneck, release planning, safe deployment techniques with rollback, and the metrics that show whether your approach is working. Every lesson ends with an exercise you can apply to your own change process.
What you will learn
- Explain the purpose of change enablement and release management
- Classify standard, normal and emergency changes and assess risk
- Design decentralised, risk-based change authority
- Plan releases and separate deployment from release
- Choose safe deployment patterns with tested rollback
- Measure change success rate, lead time and failed changes
Lessons
- Why Change Enablement Matters
- Change Types, Models and Risk Assessment
- Change Authority Without Bottlenecks
- Release Planning and Coordination
- Safe Deployment Techniques and Rollback
- Measuring and Improving Change
Self-paced course from Tech Skills Library. Educational content only; it is not an accredited qualification, licence or credential.
Lessons
Why Change Enablement Matters
Change Types, Models and Risk Assessment
Treating every change the same wastes effort on safe changes and under-protects risky ones. Classifying changes and using change models lets you apply the right level of control. The three change types Standard changes: low-risk, well understood, fully documented and pre-authorised. Examples include adding a user to a group or provisioning a server from a […]
Change Authority Without Bottlenecks
A change authority is the person or group that authorises a change. Getting authority right is the difference between a process teams trust and one they avoid. Decentralise by risk Assign authority based on risk rather than sending everything to one board: Standard changes: pre-authorised by the model. Low-risk normal changes: peer review by another […]
Release Planning and Coordination
Release management ensures that new and changed functionality is made available to users in a controlled way. Good release planning reduces surprises for users and support teams. Deployment is not release Deployment moves components into a live environment. Release makes functionality available to users. Separating them, for example with feature flags, lets teams deploy code […]
Safe Deployment Techniques and Rollback
How a change is deployed determines how much damage a defect can do. Modern techniques limit the blast radius and make recovery fast. Deployment patterns Blue-green: run two identical environments; deploy to the idle one, test, then switch traffic. Rollback is switching back. Canary: release to a small percentage of users or servers, watch metrics, […]
Measuring and Improving Change
What you measure shapes behaviour. Good change metrics show both safety and speed, so teams are not pushed to trade one for the other. Core metrics Change success rate: percentage of changes implemented without causing an incident or needing remediation. Change lead time: time from request or code commit to running in production. Deployment frequency: […]