Secondly, I am not so familiar with this project, how can I get the most project information in a short time? It is necessary to use the working platform to read the relevant materials of the project at the first time, and have a general understanding of the project. Then hold a formal internal meeting of the project team to introduce the project team members, project background, progress, etc. It also needs to include the problems encountered in the first phase of the project and what achievements have been obtained. A formal meeting can ensure the correctness of the information, and at the same time the meeting can learn about the information not contained in the document. Communicate more with the project manager and technical manager of the first phase. During the communication process, you can find the root cause of the problems in the project, and analyze the good points in the project and the areas that can be improved.
Furthermore, I am not so familiar with this product, how can I master this product in a short period of time? Some people may say that the project manager does not need to know the product very well, as long as he has good project management skills. I do not agree with this point of view. A good project manager needs to have a certain business view on the industry and products in which he is located, which can play a great auxiliary role in requirements analysis and project scope control. It also helps to have their own independent analysis to help make decisions when requirements change. There are many ways to learn quickly. I like to experience it myself, then draw a model diagram of the product, and then compare the model diagram with the model diagram drawn by the project members. In this process, there will be many concepts that are not understood, or the value of a function is unclear. This requires an empty cup mentality and more advice from PD. There is no right or wrong view on business, only approval and disapproval.
Finally, I am not so familiar with the design of this product, how can I understand the design ideas more quickly? This requires the project manager to have a certain technical background, first obtain a general understanding through the project's design documents, and then consult the technical manager or major development members in the project. In this process, posture is very important. Don’t affect your prestige among project members because you are afraid of exposing your ignorance. Your attitude is everything. As long as you are sincere and study hard, I believe you will gain everyone’s respect and favor. , because everyone feels that you are working hard, and you are on the same front as them. After understanding the design ideas, combined with the understanding of the product, you can know the dependencies between the required function points more clearly, which is convenient for the splitting of the function points and the assignment of tasks. At the same time, it can also help the project manager to have a general grasp of the workload assessment of each function point. Of course, the project team members should be trusted in workload assessment, but this can help the project manager to clarify the project risks. , which can be the most flexible and adapt to changes without change.
-----------------------------------------------------------------------------------------------------------------
The situation of taking over a project halfway is actually very common in actual work. Personally, I feel that the probability of success of the project will be greatly increased by doing the following:
1. Get to know the details of the project goals, project progress, and the impact of relevant stakeholders on the project as soon as possible;2. On the premise of good communication with the project team, integrate into the project team as soon as possible. Whether it is from personal relationships or superiors, you must let project team members listen to your commands more effectively;
3. Control project changes and identify the risks brought by changes in the process of project execution, and effectively inform relevant stakeholders of the changes brought about by changes. If the problem and impact are confirmed by the customer and the superior by signing or email confirming that the impact is acceptable, then implement the change;
4. Maintain close communication with the superior leader, so that the superior leader can always understand the real situation of sex. Don't hold back with problems, be afraid of criticism from leaders, and aim for the success of the project. In this way, the superior leaders will have a sense of participation in the project, and will take the initiative or be willing to help you solve the problems encountered in the project, and give you enough support at critical moments.
5. Maintain close communication with customers and constantly understand the real intentions or needs of customers. Let the customer know the project situation during the process of name progress, whether the product is required by the customer, and the major functional changes can be communicated with the customer and added in the next version. In many cases, customers will have real improvement needs in the process of using the product. In the progress of the project, they can only be imaginative. It is particularly important to reasonably control the needs of customers.
6. How to turn customer dissatisfaction into satisfaction is also an art.
-----------------------------------------------------------------------------------------------------------------
Preparation before taking over
Before taking over, you must first understand the current status of the project. You can consult the leader in charge of the project. Of course, if the leader fools you and tells you that this project is a benchmark, or how good this project is, then you need more Think about whether it is a hole.
At this time, you need the leader to provide a bug modification order or a requirement change order for the project, which can roughly show the problems existing in the project objectively.
If there are many things modified in the bug list, or the requirements change frequently, then it is not recommended to take over the project, otherwise you will suffer in the end. You should handle the unfinished project well, and it is your ability to handle it well Poor, other colleagues are also standing and talking without back pain to run on you.
If the project's bug tickets and requirements change orders are not very frequent, the project can still be taken over.
The first thing after taking over
Start using the project immediately, run the project process first, and then understand the design purpose of the project, because these contents are like a beacon that can point you in the general direction, and help you connect the code snippets together, put a The code of the function point is organized from the data layer, the service layer, and the controller layer.
To be able to quickly locate the relevant position, as well as familiarity with the configuration files related to the project between each layer, such as timed task configuration files, encryption and decryption configuration files, etc., to form a whole.
We have to remember that the more complex the project, the more important its purpose and design are.
Disassemble the project and write your own project documentation
Difficult projects are often due to lack of understanding. Looking at a lot of things, there is psychological pressure first. We must move forward under pressure, understand the project in modules, and understand the business through code.
A system must have frequently used modules and infrequently used modules, which can be learned from the user manual for customers.
If the project lacks a specific design specification, then you need to see how the relevant function code is written, and understand the business process by understanding the code and using the project.
At the same time, you must learn to write documentation, mainly to make yourself understand the project well. Because you took over the project, it means that whatever happens to the project is your responsibility.
Even if the problem arises due to the project design, or the development period, you have to bear it. Because writing text is not like speaking, it will take more time. In the process of typing, we will spend our time organizing language and thinking, which will allow us to find more problems in the project.
enter maintenance
When we understand the business of the project and related codes, even if we officially take over the project, we can start to deal with the actual problems in the project.
At the same time, we must develop the ability to take a look at the production log after work every day to see if there are potential problems in the project, such as excessive memory overhead, deadlock and other problems.
Look at the log mainly look at the error log to determine whether the bug presented is urgent or non-urgent. It is urgent to start repairing immediately. At the same time, write a copy of the email to the relevant leaders. (Otherwise you have dealt with the problem well, and the leader also thinks that you have no workload)
Look at the server's CPU, memory, etc. overhead. This doesn't have to be done every day.
写一些 SQL 脚本，来检测数据库表里是否出现了数据重复，垃圾数据。主要防范出现 SQL 注入等问题。
写在最后
唯有经历过以上所有步骤，我们才能成为一个专业的项目接盘侠，然后开心快乐的成长，对于之前负责项目里给你留的坑也好，bug 也罢，我们当然选择原谅他!