- Go-live readiness
- The state in which a programme can switch to the new system with known, accepted risk. It is shown by evidence for each critical claim, not by status colours.
- Go/no-go decision
- The formal decision, usually taken by a steering committee, on whether to go live on the planned date. A ChisokuLabs review ends in Go, Conditional Go or No-Go.Go-Live Decision Review
- Conditional Go
- A decision to go live once named conditions are met, each with an owner and a date. If a condition is not met by its date, the decision is revisited.
- Cutover
- The planned sequence of steps that moves the business from the old system to the new one, including the final data load, the switch and the checks before users start work.
- Rollback point
- The last agreed point in cutover at which the programme can return to the old system. It needs a tested rollback plan and a named person who can call it.
- Point of no return
- The moment in cutover after which returning to the old system is no longer practical. After it, problems are fixed forward.
- Hypercare
- The period of heightened support straight after go-live, when the project team stays on to resolve issues quickly before handing over to normal support.
- SIT (system integration testing)
- Testing that the new system and the systems it connects to exchange data correctly from end to end. It comes before UAT.
- UAT (user acceptance testing)
- Testing by business users that the system supports their processes. A signed acceptance from each business area is a key piece of readiness evidence.
- Data migration reconciliation
- Checking that the data loaded into the new system matches the source, by record counts, balances and key fields. The evidence is the reconciliation output, signed off by the data owner.
- Mock load
- A rehearsal of the data migration with production-like data, run before cutover to test load times, errors and reconciliation.
- RAID log
- A register of risks, assumptions, issues and dependencies, each with an owner. It is a source for readiness claims, not proof of them.
- Readiness claim
- A statement that something is ready for go-live, such as “UAT is complete” or “cutover is rehearsed”. Every critical claim is tested on READINESS-5.
- READINESS-5
- The ChisokuLabs test for every critical readiness claim: Status, Owner, Evidence, Date and Action. A claim reported Green with 2 of 5 is an assumption, not a fact.How READINESS-5 works
- Contradiction testing
- Checking readiness claims against each other across workstreams, for example a reconciliation reported as passed while a business entity has not signed UAT. The most expensive risks sit between workstreams.How READINESS-5 works
- Decision condition
- Something that must be true before go-live under a Conditional Go, with a named owner and an evidence-by date.