We manage go-live together with technical preparation, user acceptance, data migration, training, the support model and operational handover. With go-live planning, UAT, rollback, cut-over and hypercare approaches we reduce transition risk.
We Take the Solution Live in a Controlled Way
When development is complete or the defined release is ready for production, the technical and operational transition process begins. This stage is not only go-live; it also covers user acceptance, data migration, training, authorisation checks, the support model and operational handover.
The goal is to ensure that the developed solution goes live in a secure, controlled, sustainable way that users can adopt.
Different transition approaches can be applied at go-live depending on the project's delivery model. In predictive projects, phase closure and formal acceptance processes come to the fore; in agile projects, release-based go-live, pilot usage or gradual rollout may be preferred. In hybrid projects, the main milestones are preserved while releases are managed iteratively.
This Phase at Unitic
User acceptance testing (UAT) is a milestone of its own; customer findings are tracked by topic and tied to fixes and retests. A task's "done" status is never, on its own, evidence of acceptance or release.
Data migrations are rehearsed first with dry runs, duplicate checks and reconciliation; a controlled rollback plan is ready. New channels and features are opened gradually.
Techniques Used
- Go-live planning
- UAT management
- Cut-over planning
- Rollback planning
- Data migration planning
- Deployment checklist
- Release readiness assessment
- Pilot usage
- Phased transition
- Smoke test
- Regression test
- User training plan
- Operational acceptance criteria
- Hypercare planning
- Authorisation matrix check
- Runbook preparation
- Knowledge transfer
- Change communication plan
- Post go-live monitoring
Predictive Go-Live
In predictive projects, go-live is usually carried out in connection with phase or project closure. After deliverables, acceptance criteria and test results are complete, go-live happens through a formal approval mechanism.
Suitable Techniques
- Phase-closure approval
- Scope validation
- UAT result report
- Go-live checklist
- Cut-over plan
- Rollback plan
- Formal acceptance document
- Operational handover document
- Training completion check
Agile Go-Live
In agile projects, go-live can be designed on a release or increment basis. When working parts are ready, they can be tested with pilot users, rolled out gradually, or taken live in specific releases.
Suitable Techniques
- Incremental release
- Pilot usage
- Feature-based rollout
- Release decision after sprint review
- Improvement through user feedback
- Release backlog
- Acceptance after demo
- Gradual rollout
Hybrid Go-Live
In hybrid projects, go-live is managed according to both high-level phase and milestone plans and sprint / release outputs. This model provides enterprise control together with agile go-live flexibility.
Suitable Techniques
- Roadmap-based release plan
- Phase and release mapping
- Joint assessment of UAT and sprint outputs
- Steering committee go-live decision
- Gradual go-live
- Hypercare plan
- Operational handover
- Release readiness report
Sample Deliverables
- Go-live plan
- UAT result report
- Go-live checklist
- Data migration plan
- Cut-over plan
- Rollback plan
- User training documents
- User manual
- Operational handover document
- Support model
- Runbook
- Post-launch monitoring report