Some experiences shared by project managers during system deployment exchange meetings

Scenario 1:

During the training, I asked the project managers about the differences between hotfix and servicepack. Apart from the different time plans and the same deployment increment methods, there is actually another point:Servicepack usually includes a set of defects reported by users or discovered by users for a period of time.For more information, see 《The owner said that our project manager was very casual to launch the product "!. Many project managers were not very familiar with this issue. In fact, it is very easy to understand this sentence from another perspective:

 

If you make a product, you can sell it to multiple customers and make multiple copies on the market. If user a reports a fault to you, you decide to hotfix the function used by user a, but this function is for other users, if they are not in use or are not in use for the time being, is there no such fault risk for other users in the past? Of course the results are not. Therefore, you need to issue servicepack to users in a planned manner, and package and issue the Fault Report of the user and the defects discovered by the user within a period of time.

Of course, you have to be responsible for making products. Sanlu's infant milk powder is like a lot of copies of the products you have issued on the market. It cannot be solved by distributing servicepack!

 

Scenario 2:

The last part of the system deployment training meeting held in the previous two weeks was the previous experiences and experiences of various project managers, deploy the actual cases with deep feelings:

1. Project Manager A: in deploying hotfix for the system, conflict analysis is very important. For details, see 《How can I deploy hotfix when a bug occurs in the production environment?Step 1 in the article. During the deployment of Hotfix, only function analysis is performed, but performance analysis is missing. As a result, the data server load of the IT system is too heavy and shutdown occurs on the first day after the hotfix is launched;
2. Project Manager B: Conflict analysis is very important. Project Manager B cited the project he was in charge of. Due to lack of consideration of Hotfix, after the hotfix is deployed, hotfix is performed on the hotfix, this reduces the user's trust in the system;
3. Project Manager C: to deploy a hotfix, you must specify the hotfix deployment list and related impacts. In Project C, there is a function problem and the user complained. After analysis, the function needs to be modified, not only the WebCodeYou also need to modify the table and add a column so that the problem will not be very serious. The problem is found when the result is deployed to the production system, and the table and trigger are ignored, while the trigger still has logic processing; therefore, the deployment process is also very important. If the hotfix list has been verified on the test system, you do not have to wait for the production environment to discover the problem;
4. ...

Analysis:

The project managers asked our training instructors about how to better analyze conflicts?

The best answer to this question is the feature tracking matrix in the cmme management system. One requirement affects those functions. In those code implementations that involve the tables and logic in the background, the test cases used to test this function are displayed in the tracking matrix, if we maintain the function tracking matrix clearly throughout the process management, do we need to check this Excel table for conflict analysis?