Published May 8, 2018 — Updated June 18, 2018
This is the moment the team has been working so hard to reach. It is when you are ready to deploy a product into production and let all end users know that the application is ready for use. It is also a great opportunity for the team to celebrate and enjoy the triumph of a successful application delivery.
To go live, there are specific steps which need to be taken to push the code and any data into the production environment, where it become accessible for all users. This is the first time many end users may be seeing the new application, so it is important to be methodical and thorough in the planning and testing of this final step in the development journey. Before you can go live, there is a critical meeting where the Scrum team and the key stakeholders evaluate readiness and provide approvals for release based on a set of predefined conditions for what constitutes readiness.
With Pega, the go-live readiness is simplified through the use of Guardrail reports, PRPC logs, the Performance Analyzer (PAL), and other standard tools such as CPU utilization logs.
Additionally, Pega Global Customer Support (GCS) is prepared and introduced to the client to ensure a smooth transition into on-going support.
You won’t realize any value from a product that’s not in production. The sooner you can get a solution into the hands of end users the better. Don’t forget that end users may need support, such as training or documentation to get the most out of the product.
After the stakeholders have met and made a “go” decision, the deployment team initiates launch to production based on the pre-planned set of go-live activities and steps. The Go Live process should include validation tests, such as smoke testing, spot checks of the data in the application, and other post production success metrics defined by the team. Once production testing is completed, you can send end user communication – the final step in the Go Live process.