Different kinds of readiness
The cancellation service needs a repeatable release, reliable behaviour and people who can resolve cases and incidents. Compare approaches by the work they organise and the information they retain.
| Approach | Contribution | Connection to examine |
|---|---|---|
| A Simple Architectural Framework (ASAF) | Applies the Operating and Governing process areas across the organisation’s aspects. | Join people, suppliers, finance and business work to technical operation. |
| ITIL | A framework for digital product and service management. | Connect delivery with support, incidents, service relationships and improvement. PeopleCert overview. |
| DevOps | Connects development and operation through shared work and feedback. | Show the owners, checks and service decisions around an automated pipeline. PeopleCert on ITIL and DevOps. |
| Site Reliability Engineering | Uses service objectives and operational observations to guide reliability work. | Relate technical reliability to the user’s service and the decisions about improvement. Google SRE Workbook, 2018. |
| OWASP Software Assurance Maturity Model (SAMM) | Includes secure deployment and operational security practices. | Retain security checks and response capability after release. SAMM model. |
These rows draw on selected public references. Their practices can coexist in one method. An automated release pipeline supplies some of the checks needed for service introduction; the service owner also needs to know whether people, information and support arrangements are ready.
Trade-offs
A small release can shorten feedback and simplify recovery, while still requiring coordinated data, staff or supplier changes. A larger cutover may reduce the time spent supporting two arrangements but increase the work that must succeed together. Examine that trade-off in the actual service.
Methodology configuration
Relate each practice to the release and operating records your team already uses. Use Methodology configuration to map terms, records and reviews to your own approach.
Use the operating example, then adapt the readiness and support record to retain service acceptance, recovery responsibilities and unresolved work.