Week 7 of 8
Cutover, go/no-go and hypercare
Infor’s guide asks for a detailed cutover plan and a checklist-based go-live readiness review across solution, technical, data, people and transition readiness. That is the shape of a good go/no-go meeting: short, because the evidence was collected in advance.
On multi-tenant CloudSuite there is one more item for the checklist: the next Infor update. Know its date before you pick yours, so your first weeks live are not also your first regression cycle.
This week: build the runbook and the readiness checklist
- Build an hour-by-hour runbook with owners, timings, validations and a marked point of no return. Include stopping, draining and restarting each ION flow.
- List go/no-go criteria with thresholds and evidence: SIT and UAT exit, reconciled dress rehearsal, every interface Ready, roles in production, support readiness.
- Check the deployment calendar: if a feature release or monthly update lands in your first weeks live, plan its regression into hypercare.
- Set hypercare exit criteria on evidence: no open severity 1 for an agreed period, first month-end close done, ION error queues at steady state.
Number of the week
48 hours
is how far ahead the go/no-go checklist should go out, so the meeting reviews evidence instead of collecting it.
Source: The Sign-Off Table go/no-go checklistUse this week
- Cutover Plan & Runbook →
Tasks, timings, validations and the point of no return.
- Go/No-Go Readiness Checklist →
Criteria with thresholds, blocking flags and an automatic recommendation.
- Hypercare Plan & Exit Criteria (Word) →
Command center rhythm, KPIs and measurable exit criteria.
Next week, the last of the playbook: living with Infor’s updates, Release Reports and feature toggles.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.