How to Be a good project manager

Recently, I just created a project as a project manager, a feature manager, or a product manager. It's all about that. I took a few people and a dozen people to complete a project, I have learned a lot. Of course, it is also annoying and tiring. Keep a record of what you want to do in the new year.

 

Do this project is in the IPD-CMMI process, take a project to learn the best is the first three axes:

(1) grasp the solution

(2) Plan

(3) Standards

 

Putting the solution first may vary with the company, but for our most basic management, such management is actually not much management. Therefore, PL itself is an SE and must control the solution. There are several advantages to be familiar with the solution. First, we can clarify the workload, and second, we can improve our technical skills so that we will not stop using the solution. Third, we will drive the team. How can I bring a team to serve you? You are better than others, and the solution is yours. People follow your plan, which naturally improves your prestige. Do not leave technology alone, especially for the new PL.

 

With the clear plan, we can basically clarify the workload. At this time, we need to make a plan based on productivity. There are two factors to consider in planning: first, the above, and second, the actual capabilities of the team. Therefore, when you plan, do not make the decisions by yourself. You must solicit broad comments. When preparing a plan, developers can usually participate in the plan through some common methods in the industry, such as the dephi method. In this case, the deviation of the plan is much smaller. Then compare the plan with the big version plan given above. If the plan is consistent with the plan, the plan will have to be pulled.

 

Individuals tend to follow the developer's plan. At this time, PL plays a very important role. We must argue for it and try not to seek perfection. Based on their own experience, there will be basically no delay in the construction period, and most of the time given above is actually unreasonable, and they do not know how long it will take. But the difference is the problem.

 

With solutions and plans, the next important thing is to clarify standards. What standards? That is, what is good and what is poor. Because after a period of time (for example, three months or half a year), there must be an assessment, so the standards should be clarified from the very beginning. On the one hand, we can let everyone have a direction in their daily work and understand the expectations of the supervisor. On the other hand, we will not be confused about many things. Of course, it is very easy to develop software standards. Standards of compliance: pass the test, and transfer the test quality is the final standard. But in the process, if you want to do better, you must pay attention to programming specifications, quality control, and so on. When setting this standard, we also need the participation of team members to reach consensus. Do not ask the project manager to unilaterally say what is good or bad. Be sure to explain questions to team members.