...
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.