Project Management

Please login or join to subscribe to this thread

Go live template

linkedin twitter facebook  
avatar
Shweta Mishra Product Owner| T Mobile Prague, 10, Czechia
Hello colleagues,
Do you have any go-live template , or check list which can be referred for creating go-live plan for major release done by cross functional multiple team?
And does it have UAT or beta testing mandatory criteria ?
Any reference or template would be very helpful!

Many thanks,
Shweta
Sort By:
avatar
Abolfazl Yousefi Darestani Manager, Quality and Continuous Improvement| Hörmann-TNR Industrial Doors Newmarket, Ontario, Canada
No. I don't.
avatar
Aaron Porter
Community Champion
IT Director| Blade HQ Payson, UT, United States
Have you searched the templates section? This was one of the first results I got:

https://www.projectmanagement.com/delivera...deployment-plan

I'm not saying it has exactly what you're looking for, but you should be able to find a few to compare.

I probably have some old go-live plans I could track down, but I'm not sure they would help as they were focused more around SAP and Magento launches. Other web launches and mobile work has been more checklists than formal plans.

There may be similar steps in different types of go-live events, but the decision points can be vastly different. That's why I doubt my old files would help. I also have not included beta or UAT testing in my go-live plans. There were a couple of projects where UAT went down to the wire and almost became part of go-live, due to some major defects, but I've planned it separately and treated it as more of a phase gate to the go-live plan.

Some things you should consider:
- Pre-go-live activities - does anything need done after the Go/No Go decision but before Go-Live officially starts?
- Go-live activities to perform
- Timing for activities
- Dependencies between activities
- Roll-back plan and point of no return
- Communication plan, including milestones for when updates will be sent out
- Post-launch validation
- Down-time window/maintenance pages (if you need downtime)
- Time zones of the go-live team, if geographically diverse
- Verify there are no conflicting business events or deadlines that the launch would interrupt - Sales and Finance especially
- "Vendor" availability, if working with a vendor or receive support from a third party
- Go-live walk-through meeting with schedule "handouts" (can be digital). This gives the team the chance to give feedback on the schedule and commit to their part(s)
- Does your company require formal review to schedule the launch? I worked at a company where we were expected to submit a change request and then represent the request in a technical change board meeting where we would also look at what else was going on for the planned time, to avoid scheduling conflicts.

I hope this helps.
...
1 reply by Shweta Mishra
Aug 26, 2022 12:13 PM
Shweta Mishra
...
Many thanks Aaron!
avatar
Shweta Mishra Product Owner| T Mobile Prague, 10, Czechia
Aug 26, 2022 10:31 AM
Replying to Aaron Porter
...
Have you searched the templates section? This was one of the first results I got:

https://www.projectmanagement.com/delivera...deployment-plan

I'm not saying it has exactly what you're looking for, but you should be able to find a few to compare.

I probably have some old go-live plans I could track down, but I'm not sure they would help as they were focused more around SAP and Magento launches. Other web launches and mobile work has been more checklists than formal plans.

There may be similar steps in different types of go-live events, but the decision points can be vastly different. That's why I doubt my old files would help. I also have not included beta or UAT testing in my go-live plans. There were a couple of projects where UAT went down to the wire and almost became part of go-live, due to some major defects, but I've planned it separately and treated it as more of a phase gate to the go-live plan.

Some things you should consider:
- Pre-go-live activities - does anything need done after the Go/No Go decision but before Go-Live officially starts?
- Go-live activities to perform
- Timing for activities
- Dependencies between activities
- Roll-back plan and point of no return
- Communication plan, including milestones for when updates will be sent out
- Post-launch validation
- Down-time window/maintenance pages (if you need downtime)
- Time zones of the go-live team, if geographically diverse
- Verify there are no conflicting business events or deadlines that the launch would interrupt - Sales and Finance especially
- "Vendor" availability, if working with a vendor or receive support from a third party
- Go-live walk-through meeting with schedule "handouts" (can be digital). This gives the team the chance to give feedback on the schedule and commit to their part(s)
- Does your company require formal review to schedule the launch? I worked at a company where we were expected to submit a change request and then represent the request in a technical change board meeting where we would also look at what else was going on for the planned time, to avoid scheduling conflicts.

I hope this helps.
Many thanks Aaron!
avatar
Verónica Elizabeth Pozo Ruiz RYLAI Access Control Quito, Pichincha, Ecuador
This article would be helpful for your needs: https://www.airiodion.com/go-live-checklist/
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
In our case we have three key activities: UAT (User Acceptance Test), Tansition and Cutover, Go Live. Following it we have the Hypercare. Them happends no matter the approach we take (Tranditional, Lean, Agile, etc). UAT is not a beta testing for us, is the moment where people that expressed the needs agree on the solution adressed those needs. While we have a basic "template" each one has to be adjusted for each initiative. The key input of the UAT are the test cases which are primary focused on the objective I stated before. Transition is about to care that all activities to put the solution in place and ready to be used have been covered. For example, end user training if applies. Cutover is about the final activities to release the solution. Hypercare is a time of period in wkich any incident is taken directly by the team which created the solution. All of them have a checklist and an associated plan. Both very simple but effective about to assure the quality of the solution.

Please login or join to reply

Content ID:
ADVERTISEMENTS

Don't be humble. You're not that great.

- Golda Meir

ADVERTISEMENT

Sponsors