Skip to main content

Go-Live event

Definition of Go-Live

Go-Live refers to the actual launch of the application into the production environment. It requires a Go-Live decision from the project team and sponsor to move forward. Most Go-Live events include cut-over checklists and communications in the form of a run book, release plan, or implementation plan. For example, a release plan lists the sequence of activities required to move the application from a development/staging environment to a production environment. Checklists help you track the progress of activities within a system downtime window and coordinate hand-offs between different teams for dependent tasks. 

Note: The Go-Live communication is designed to inform all users of the application change and document how issues will be resolved. Change management activities and end-user communication is the responsibility of the client's internal communication team. The Scrum master ensures communications are coordinated between project teams and stakeholders.

In the following image, click the + icons to learn more about activities that take place during the Go-Live event.

Release Support Plan

The Release Support Plan outlines how users can report problems. It includes actions the support team must take to resolve and escalate production issues. As part of the Go-Live preparation activities, the support team receives application training. You work with the support group to document and deal with incoming issues. 

Support activities typically include:

  • Known issues – The team identifies and communicates all known issues and any workarounds to end users and support staff.
  • Issue resolution – The support team reviews, assigns, and escalates issues appropriately for fast resolution.

  • Onsite team members – It is helpful to have a team of subject matter experts (SMEs) on-site with end-users at Go-Live to answer questions.

To find answers or raise tickets across all Pega products and services, go to Pega Support.

Release automation tools

It is a best practice to automate the deployment process throughout the Build and Adopt phases using either a third-party tool or Pega’s Deployment Manager application. The Deployment Manager tool within Pega Platform™ provides your DevOps team with extensive automation to support the Continuous Integration and Continuous Delivery (CI/CD) pipeline in a model-driven manner. Deployment Manager is installed on the orchestration server, on which release managers configure and run pipelines. You can run application updates with the click of a button to execute automated tests, run reports, view diagnostics, and manage rollbacks.

With the Deployment Manager, you can fully automate your CI/CD workflows and see the run-time view of your pipeline, including:

  • Branch merging
  • Application package generation
  • Artifact management
  • Package promotion to different stages in the workflow

For more information and downloads, see Deployment Manager on Pega Marketplace.

Check your knowledge with the following interaction.                                  


This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice