Introduction
The Go-Live Phase is the second phase in the no-code project delivery lifecycle, as defined in the No-Code Playbook. This phase follows the Design Phase and focuses on moving the no-code application from design to production, ensuring it is functional, meets business needs, and adheres to organizational governance and security standards. The primary objective is to build the Minimum Viable Product (MVP), gather feedback, and prepare the application for its first live release.
Objectives of the Go-Live Phase
The key objectives of the Go-Live Phase include:
Building the MVP: Taking the design and functional requirements from the previous phase and creating a working version of the application that delivers core functionality.
Gathering Feedback: Ensuring the application is tested by key stakeholders and users to validate the design and refine functionality based on real-world usage.
Ensuring Compliance and Governance: Conducting necessary security, compliance, and governance checks to ensure the application meets organizational standards before its release.
Executing the First Release: Preparing the application for deployment to its intended users, ensuring that everything is in place for a successful launch.
Stages of the Go-Live Phase
The Go-Live Phase consists of four key stages, each designed to refine and prepare the application for its initial release to users:
Stage 5 - Prototype to MVP: In this stage, the initial prototype created during the Design Phase is further developed into the Minimum Viable Product (MVP). This includes building core features, testing functionality, and ensuring the application is usable. The MVP should solve the essential business problem while leaving room for future iterations and enhancements.
Stage 6 - Feedback Loop: Once the MVP is built, it is tested by key stakeholders and early users. This stage is critical for collecting feedback on how the application performs in real-world scenarios. Feedback gathered during this stage is used to make improvements and adjustments before the official release.
Stage 7 - Governance Checks: Before the application can be released, it must pass a series of governance checks. These include compliance with security protocols, data governance policies, and any regulatory requirements. The Governance and Compliance Officer, along with IT operations, ensures that the application is secure, stable, and ready for production.
Stage 8 - First Release: After passing the governance checks and incorporating stakeholder feedback, the application is prepared for its initial deployment. The first release is a major milestone, as the MVP is made available to a broader audience, and the business begins to see the value of the no-code solution.
Importance of the Go-Live Phase
The Go-Live Phase is essential for turning the vision of the application into reality. It transforms the concept from the Design Phase into a working, usable product that delivers immediate business value. By gathering real-world feedback and ensuring compliance with governance standards, the Go-Live Phase ensures that the application is not only functional but also scalable, secure, and aligned with business goals.
Once the first release is complete, the project transitions to the Everyday Delivery phase, where ongoing improvements and iterations are made based on user feedback and performance.