LinkedIn
Copied!

Go live

If the go/no-go decision is to ‘go’, it’s time to initiate your go live activities and steps. Your go-live process should include validation tests, such as smoke testing, data spot checks, and other post-production success metrics defined by the team. Best practice is to automate the deployment process throughout the Build and Adopt phases using either a 3rd party tool or Pega’s Deployment Manager.

The Deployment Manager provides DevOps capabilities with extensive automated tools to support the Continuous Integration and Continuous Delivery (CI/CD) pipeline in a model-driven manner. You can run deployments involving your application updates with the click of a button which will execute automated tests, run reports, diagnostics and manage rollbacks etc.

You will execute your pre-prepared run sheet and post-go-live support plan which would typically include;

  • A review and triage of smoke test results to determine if go-live can proceed
  • Once production testing is completed, you can send end-user communication; the final step in the Go-Live process.
  • Deploying floorwalkers or remote support working directly with the business to help with any emerging issues during the first few days

What happens next? The Journey to adopt the new solution has just begun. A release going live is not necessarily the end of a project.  Usually it is just the first release, which you will learn from to improve the next release. The first release should be monitored and enhanced based on user feedback and outcome metrics. You can review analytics and usage patterns to see if the usage is as expected, or determine what should be changed. This can all be wrapped into planning your next MLP.

The related content links below provide methods and tools to help you.

Suggest Edit

100% found this useful


Related Content

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.