It has been more than a year since I joined the company to manage product releases, and there have been dozens of system upgrades and releases in the past year or so. so
For the product launch I made some briefings myself, as follows:
1. The release content and release time must be notified to all relevant stakeholders in advance.
2. The impact of the published content on the stakeholders must be assessed in advance and considered clearly. If the stakeholders have any objections, they must be recorded, discussed and confirmed.
3. There must be a pre-assessment of the possible impact after the release, and possible countermeasures should be taken, such as the extraction arrangement for the possible increase in the workload of operation and maintenance and customer service.
4. Try to avoid publishing during the peak hours of user usage, and try to choose a time period with a small number of users, and 1 or 2 days after the release should also be a time period when users are less used.
5. When releasing to the official version, try to perform more than one simulation upgrade and simulation test as much as possible.
6. After the release, the system update log or system announcement must be released.
7. If a shutdown operation is required at the time of release, all relevant stakeholders must be notified in advance.
8. After the release is completed, you must pay close attention to the monitoring status of customers or operation and maintenance.
9. Make a backup before publishing, just in case, you know this.
In fact, all these matters are summed up in one sentence, which is to tell the relevant personnel clearly and clearly what you are going to do, and make all preparations in advance before doing it, and have various emergency plans after the event.
Reprinted in: https://www.cnblogs.com/kevinGao/p/3589952.html