Go live

This go-live protocol is tailored for tasks residing in the "Waiting to Go Live" column, having successfully passed all preceding stages detailed in the Development Team Workflow.

Testing and Quality Assurance

Ensure comprehensive testing of the feature across development and testing environments. Execute functional, integration, performance, and security tests as required.

Backup Procedure

Before deployment, switch to the master branch and create a backup of the current application onto a new branch. This precautionary measure safeguards against potential disruptions post-deployment, allowing swift recovery and implementation of fixes if necessary.

Deployment Strategy

Schedule deployment during periods of minimal user impact, typically between Monday and Thursday, preferably in the early morning or afternoon. Avoid late-day deployments to minimize support risks.

Post-Deployment Validation

Verify feature functionality post-deployment in the live environment. Promptly address any identified issues to maintain operational integrity.

During the initial 15 minutes post-deployment, provide a brief overview of key app features, highlighting any critical issues such as onboarding failures or display anomalies.

Feedback Collection

Gather user and support team feedback to assess feature performance and user satisfaction. Document feedback for future enhancements.

Monitoring and Support

Continuously monitor feature performance in the live environment and promptly address any technical issues or user concerns. Offer necessary support to ensure uninterrupted functionality.

Notification

While primarily the PM's responsibility, stay abreast of release notifications to understand team dynamics and cross-divisional communication within the team.