/
Common Cutover Sprint

Common Cutover Sprint

Owned by Jan Kubica
Dec 12, 2024
2 min read

Goal for the sprint:

  • Prepare the production partition for the business Go-Live. 

Prerequisites

  1. The UAT has finished and you have the acceptance protocol signed or GO decision in written.

  2. The PROD partition is in place

  3. The Cutover plan is ready. Use the Cutover planning template.

  4. The resources are ready

  5. Creating the calendar entry in the 'Functional Lounge' calendar to announce the go-live to support.

  6. https://pricefx.atlassian.net/wiki/spaces/CUST/pages/2088699669 done

Actions:

  1. Hint: create a new sprint in Jira (“Cut-over”)

  2. Prepare an exact and comprehensive (list of logics, jobs, tables etc...) environment update plan for Production (based on experience with previous update of QA environment). In case our operations team need to do actions (e.g. set up a new instance, or copy an instance) please take the lead time they need for these actions into account - this can be up to one week.

  3. Revision of the documented implementations.

  4. Training for super users.

Artifacts:

  1. Cutover planning template

  2. Status report 

  3. Calendar entry in the 'FunctionalLounge' calendar

Checklist for Cutover:

  1. The cutover plan has been prepared and agreed by client and Partner/PriceFx.

  2. The PROD partition is up and running and customer has access to the partition.

  3. https://pricefx.atlassian.net/wiki/spaces/CUST/pages/2088699669

  4. The solution has been signed off to be deployed in PROD. Final check by the PM.

  5. The technical Go Live date is scheduled and resources are allocated.

  6. The solution (=configuration) is deployed to PROD partition.

  7. User accounts are created.

  8. Data loaded to PROD.

  9. Integrations are switched on by IE.

  10. Smoke test.

  11. Go-live.

Notes

  • Solution Sign-off = acceptance protocol concluded.

  • Cutover might get split into two milestones:
        1. Technical Go-live: all configurations are delivered, all data loaded, all interfaces active. Smoke test performed after UAT.
        2. Business Go-live: at least 1 real end user is using  the software and benefiting from it.

Check with the customer, and adjust the plan accordingly.