In the project process, through observation, we feel that the role of PM should be well performed in the following aspects:
-
- Be familiar with key project details
Although PM does not participate in specific coding, it does not mean that you do not need to know the specific implementation details, especially the key points that affect project success or failure. Some PM is getting farther and farther away from technology, and it is unclear how some functions are implemented, what technologies are used, and where special attention is needed. This will greatly affect his decision-making and judgment, especially when dealing with emergencies. At this stage, especially when the project scale is small, it seems that PM is better to serve as an architect.
-
- The time of each stage of the project should be clear enough
PM has a clear project roadmap at all times, and prepares for each time point. For example, estimate the workload and resource allocation before the project is established, coordinate the time points and fault tolerance plans with other teams; organize the project backbone to understand the requirements and design the architecture before the Requirement Review, and conduct in-depth discussions with the PD to avoid business interruptions; prior to the design review, all risk points and partners should be evaluated, the design documents should be completed, the Cooperation details should be fully discussed with the partners, and an agreement should be reached; prior to the submission of the test, the progress of each task should be noted, in particular, it is risky to prepare the environment for testing. Before developing joint debugging, contact the contact persons of all participants and prepare the environment. Make a release plan before release, estimated risk points of departure deployment. In short, you need to have a clear understanding of each key time point, prepare in advance, and control risks.
-
- Handle relationships with other teams
The success of a project is not achieved by your own team. It requires the cooperation of all teams. Therefore, it is necessary to learn to deal with other teams, the contact person who communicates with other teams is PM, which plays a decisive role in ensuring smooth cooperation between teams. First, you need to find out what is a matter of principle and what is a matter of concession. When there is a difference, you need to immediately determine whether a concession can be made. In addition, you must keep your questions in the front and communicate with each other in advance. As long as you are all trying to make the project well and discuss these possible differences before they arise, there is nothing to deal. Finally, I learned to deal with all types of people. Lin zida had all the birds. communication was not to win or lose, but to reach an agreement. There were more skills in this field, learning and accumulation are required.
- Mobilize the enthusiasm of the team members and try to make things easier for others.
In a previous project, PM is very dedicated and many things are done by myself. The result is a very bad phenomenon. Every night, when all of his project members are gone, they leave him alone and work hard. As a result, each release has many problems and is thrilling. This shows that you are not alone in the team, and you should not rush to the front line. PM's sense of accomplishment should not be done by yourself, but by your actions, your team members have done things well. Only in this way can the project team be fighting, and other Members want to reflect the value in the project process. You need to learn to train and train other members, to maximize their potential, this is why Nash is more likely to win MVP in the same outstanding circumstances.
-
- Handle risks
PM can throw points that do not affect project success or failure to those you trust, but pay enough attention to those risk points that will lead to failure. I used to bring a small project. Everything else was done very well, things were done very well, and bugs were not detected, but there was no review of several of the SQL statements that were relatively error-prone, however, when QA told me that I didn't take a look at the bug. As a result, it implies a deep-seated bug, which was exposed online, causing great losses and adverse effects. In fact, later I summarized it and found that there were obvious omissions in this SQL statement. If we carefully review it and examine the test case, we should be able to find the problem. PM must have a ledger for each risk point, and the project may not be beautiful, but if there is any negligence on the risk point, it is a failure.
-
- Arrange the task and clearly understand the task progress
PM needs to have a deep understanding of their team members, understand their abilities and interests, assign tasks to the most appropriate people, maintain in-depth communication with them, and understand the difficulties they face, although you are not the person who directly completes the task, you must be the person who helps others complete the task. The task wall is a good way to let yourself and others clearly see the completion of each task, and follow up
- Maintain a clear idea and reserve measures to respond to various emergencies
People who need to keep their thinking clearly in the project are pm, and others can be confused, but PM must not be chaotic, especially when there is an emergency. Therefore, it is necessary for PM to consciously exercise its ability to withstand pressure, such as doing more project release, design review, and data correction, and to consciously reserve some emergency solutions, suchCodeRollback, urgent release, and so on. In addition, to clearly understand the dependency between teams and systems, this dependency is often the root cause of the event.
-
- Maintain a peaceful attitude and consider the issue from the standpoint of others.
The project will be very popular, and members of the project will also have a fierce debate. In this case, it is important to maintain a peaceful attitude. A peaceful state of mind often leads to peace of mind and a more chaotic situation. There are many ways to maintain a peaceful attitude. One of the most important is to consider the issue from the standpoint of others. Once you are considerate of others, intense emotions will fade away, in addition, as a result of this kind of communication attitude, the divergent Parties will also consider it for you, which is very helpful for solving the problem and reaching an agreement.
-
- Strengthen project automation capabilities
If all the details of the project are completed by humans, risks will be greatly increased. The biggest tool to reduce risks is to complete some work with mature automated solutions, in particular, project construction, continuous integration, and release. PM should have more brains on how to make daily work flow and tools, and agile development provides many good ideas and solutions.
-
- Consensus and resolutions should be sent to relevant persons by email
There will be many changes in the project process, and the problems cannot be defined in the requirements and design documents. To solve the problem, a temporary resolution must be sent to relevant persons by email, not just Zhihui, more importantly, the provision of evidence for resolutions, which are temporary resolutions that often lead to problems and need to be used when the issue produces traceability responsibilities
- Listen to the comments of the team members and give them enough space to play.
The team members, especially those who bring projects to large companies, are all development elites and are not willing to be a mechanical coder. Therefore, they learn to listen to their ideas and learn more about what they want, to meet their growth needs as much as possible, even if they cannot adopt their suggestions for Objective Project reasons, they must make the truth clear and make decisions in a strong way, after all, the requirements and management of technicians are different.
-
- It is not based on the individual's wishes.
PM is also a person. It is inevitable that people will have personal emotions during their daily work. However, PM should be aware that there is another team behind him, and their emotions and statuses are closely related to him, therefore, when talking and doing things, you must think twice about the impact on others. Do not scatter your attacks and lose the trust of your colleagues.
There are many other important points that need to be summarized in practice.
