Readiness Review
Medium and high impact releases checked before they go to the CAB: every affected group told and trained to the target, and super users in place where the impact is high. Anything not ready does not go.
Why it matters
Releases fail with people, not code, when staff learn about a change on the day it arrives.
- When
- Weekly, before the CAB
- Length
- 45 min
- Led by
- Change, comms and training lead
- Draws on
- Organisational change management; ITIL release management
Draws on
Led or owned by
The rest of this page is for subscribers
Subscribe to read the other 4 sections of this page:
- How to run it
- Rules
- In the DelPulse workspace
- If you use Jira or Azure DevOps