Team Management in project management practice

A system requires not only excellent analysis and design, but also a good process to transform it from a blueprint to implementation. In this process, the most important thing is team management, that is, people management. The performance of a good team is quite different from that of a bad team. The ratio between them is not expressed by a quantifiable number like or. Just like a team building a skyscraper standing on the clouds, the building of another team is not as high as 10 tall! This is a qualitative difference and also a difference in the soul of the team.
The team leader is the project manager. His abilities/qualities directly affect the project's success or failure! We do not need all the members of a team to be excellent, but to ensure your project is successful, please hire a good project manager!
In the past, I used to work alone. At most, I also cooperated with two or three people, and the project was progressing well. Now responsible for the development of a large project, you need to coordinate the entire team member to ensure the progress of the project. I thought this was a very simple thing, just like before. As a result, as the project progresses, there are more and more problems, most of which are not technical, but management and coordination of team members. We need a lot of effort to make a team efficient and efficient. The following points are summarized from my previous practices. I just summarized my experiences and did not intend to write a complete paper on team management, after all, your skills in this aspect are quite simple. I hope to share my experiences in this area with you. You must pay attention to the following aspects for team management:

(1) Let the right person do the right thing. Understand the knowledge structure and background of each member, know what they are good at, and assign tasks to the people who can solve the problem most effectively and quickly.

(2) document the main functions/tasks of the project in the form of a list, and form a list of phase tasks of each member. This is important. Otherwise, you and your team members will often forget what the goal is and what they want to do.

(3) do not give our team members a feeling of no worries about our projects. Give each member a sense of urgency. A comfortable/lazy group cannot submit a project by quality on time, even if the project is not urgent.

(4) prior to submitting the previous phase of a Member's task, the next phase of the member's task should be arranged. Do not let any member idle. No matter when the system needs to be improved, reconstructed, or organized by any module, our design/implementation will never be good enough.

(5) clearly and clearly tell your team members what you want for a specific link. Otherwise, you are ready to tell the team members the same thing for the second and third time. It is not easy to let another person fully understand your intentions.

(6) fully communicate with each other. In this project, the communication between you and your team members may be far from enough!

(7) exercise/guide your team members and trust your team members. If you are a good programmer as a project manager, never believe that you can complete all the main/core functions. You may be able to complete a certain module, but more modules are completed by your team members.

(8) never stand alone. Maybe you firmly believe that your solution is excellent, but if your team members propose a new solution, please pay attention to it, and select the one that is more suitable for the current project from these two schemes. I absorbed a lot of wonderful ideas from my team members and applied them to projects.

(9) Resolute execution! The premise is that you must have enough judgment and determination power. When there are no conclusions on some topics, you need to make a shot.

(10) Treat each member fairly and fairly. Never favor any one!

(11) Remember that the project manager is not an "official ".