Operational acceptance and go-live readiness
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
verify the solution can be run, and decide go-live readiness from evidence.
Planned topics
- Operational acceptance checks monitoring, alerting, runbooks, backup and restore, support rota, access, and escalation paths with vendors.
- Verify by doing: restore a backup, trigger an alert, run an incident drill, not by reading a checklist.
- Readiness combines functional results, NFR evidence, operational acceptance, migration and rollback readiness, and open risks.
- Recommend go, conditional go (with named conditions and dates), or no-go; trace each to evidence.
- The business accepts residual risk explicitly; the architect does not hide it.
Draft outline details
Demonstration
a go-live readiness table: criterion, evidence, status (met, partly, not met), residual risk, owner; with a final recommendation line.
Check your understanding
What is a conditional go?
Show answer
Go-live approved only if named conditions are met by given dates, with an accountable owner.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.