WEB Project Manager manual-[7] What the project manager needs to remember

1. The project manager is not responsible for managing people, but for supporting people.
Resolution: not only is it a project manager, but any manager's position is like this. But in reality, many people do not do that, which is why they fail to succeed in the project. As a project manager, we must first correct our attitude and recognize the nature of this job responsibility.

2. A good start is half the success.
Analysis: the failure of a good project is often due to the lack of preparation and poor planning. Therefore, in the initial stage of the project, we should be willing to spend time collecting, discussing, and preparing technical resources in the early stage. Although the preliminary work does not seem to produce benefits directly, this work is done well, and the subsequent work will often get twice the result with half the effort. Otherwise, insufficient preparation may lead to various problems in the project (for example, a large number of demand changes ).

3. What kind of project is most likely to succeed? The answer is: the smaller the project, the more likely it will be to succeed.
Analysis: the project manager and related personnel should carefully evaluate the cost/value ratio of the feature in the project to minimize the product scale.
Sometimes the project manager may not be able to change the overall project scale, but the project manager can "narrow down" the project by various means, such as phased development and iterative development.

4. Any work unrelated to project improvement is a waste of time.
Resolution: during the project process, the project manager should not do superficial work or do meaningless work for the project itself. For example, an endless meeting; requires the preparation of detailed and ultimately useless documents.
 
5. user participation is an important guarantee for project success.
Resolution: users can be product managers, demand side representatives, or customers.
In each stage of the project, the project manager should actively ask users to participate in the project process. Through continuous communication and feedback with users, the final product is what the customer really wants.

6. Don't think that you can leave the task to a team member. You can leave it alone during this period. At the time of completion, he will naturally submit the task. This idea is very wrong.
Resolution: this will undoubtedly increase the risk of the project. It is easy to see that the task to be completed is not completed on time, and there are some delays. In this way, the subsequent work of the project will be restrained.
The correct method is: After you schedule the task, you need to regularly communicate with the members and ask if support is required so that we can ensure that the task can be completed on time and in good quality.

7. Tips: when communicating with relevant personnel during the project, do not always think that the other party's starting point is to consider the project's interests. He/she must first consider the personal interests or the department's interests, so what the project manager needs to do is: how to direct the personal interests (department interests) of the other party to the same project interests.

8. "working overtime" is a dangerous signal, indicating that there must be a problem somewhere. Find out the cause of the lag.

9. Before the project starts, the project manager must find out who is the project's decision maker and who has the final say to the project's products.

10. What we deliver is notProgram, But products and services.