Most outages involving release quality acceptance criteria are triggered by a change somebody considered routine. Technical debt in acceptance criteria is borrowed against future delivery capacity, at compound interest. It is written for people who have to make the wider technology and systems delivery agenda work with the resources they already have. Buying a tool rarely fixes release quality acceptance criteria; the underlying capability has to be built internally first. Participants apply this strand of technology and systems delivery to their own technical platform throughout, so the output is directly usable. It concentrates on the parts of acceptance criteria that determine outcomes and treats the rest proportionately. The course leaves participants able to diagnose weaknesses in release quality acceptance criteria before they become incidents. The most reliable predictor of sound acceptance criteria is whether anyone reviews it when nothing has gone wrong. Participants leave with a plan for the technology and systems delivery discipline sized to what their organisation can realistically absorb.
Expected Learning Outcomes
✓
Apply a repeatable review cycle to release quality acceptance criteria and act on what it produces.
✓
Structure the service desk and support model for acceptance criteria.
✓
Secure the software supply chain and dependencies within release quality acceptance criteria.
✓
Identify the failure points in acceptance criteria most likely to cause loss, and control them first.
✓
Test release quality acceptance criteria under realistic load before it meets real load.
✓
Plan capacity for acceptance criteria against measured growth rather than optimism.
✓
Assign clear ownership for each element of release quality acceptance criteria across the functions involved.
