Introduction: Before, during and after the release of the system version, the CutoverPlan plan is introduced. Especially when multiple related systems have dependencies, it is necessary to uniformly align each execution item and focus on dependencies of the cutting plan. There are 14 related systems in the recent major version of the Zhongtai project, and dozens of people have participated in the execution of the cutting plan. This article mainly introduces the relatively general cutting plan template and the issues that need attention in actual operation.
Template fields:
| Serial number | Numbering | System Center | Starting time | End Time | Duration (minutes) | Dependency | System involved | Task category | Task item | mission details | Executor | principal | status | annex | Task notes |
Key field description:
Number : xx-xxxx; the first two digits represent the system number, the last four digits represent the task item number, for example 01-0010
Task category: configuration check, environment check, deployment preparation, product release, product deployment, traffic switching, data backup, verification check, regression test, data cutover, system online, functional verification, data verification
Status: not started, completed, delayed
To output an executable floor cutting plan, the following processes are often required:
- Cutting plan preparation kick-off meeting
- Initial review of cutting plan
- Cutting plan review (multiple review and revision, Lacy communicates opinions)
- Cutting plan closure
Precautions:
- In the review stage, the person in charge of each system needs to explain their cutting plan task items, clarify dependencies, and ensure that relying parties participating in the online cutting know the pre- or post-execution items.
- The cutting plan includes the follow-up items before, during and after the launch. The execution time of each follow-up item is estimated to [minutes], and the task status needs to be updated in time after each task item is executed.
- The task item and task description corresponding to the task category must be detailed in the execution instructions of each step.
- Clarify the sole executor and the person in charge. Generally speaking, the executor and the person in charge are not the same person. The person in charge is often the superior of the executor. The current practice of the project is that the executor is the system TL, and the person in charge is Party A who is responsible for the corresponding system people.
- The review process of the cutting plan will also be accompanied by the completion of the follow-up tasks before going online. Generally speaking, the updating of tasks before going online is a dynamic process (before the cutting plan is sealed).
- After many reviews and updates, everyone is very clear about the system in the cutting plan and the related matters that others rely on or rely on. Once the cutting plan is closed, everyone only needs to execute it according to the cutting plan time point. The cutting plan task status needs to be updated in time. Here, the cutting plan document needs to be supported by collaborative office tools. Here, Dingding-online editing group shared files are used.
In addition, if there are too many tasks involved, it is often necessary to add a real-time progress Kanban statistics, including the following:
- Number of overall tasks
- Number of tasks currently completed
- Current number of delayed tasks
- Overall plan completion ratio
- Overall actual completion ratio