Personal Accomplishments of project managers

I don't know what the project managers of other companies do. I feel that our project managers are basically responsible for project management, technical managers, and post-design, at present, this is a domestic project at hand. It is also the most tiring one I feel. It has encountered many problems and gained a lot of experience. In the past, I always felt that the project manager was quite good. Now I understand that I still have many shortcomings.
There are a lot of theoretical books on project management. The following are my personal experiences. I would like to write them down and remind myself that I want to learn from the programmers who just entered the project.

1. Be technically competent. I have always thought that a project manager without technical knowledge cannot become a good project manager.

Technically superior, you can easily establish personal authority. Programmers are a group of proud people. Although there is a company's system, the role of personal charm in the project cannot be ignored.

By understanding the technology, you can accurately arrange the project progress and effectively identify the difficulties and risks in the project.

Understanding technology can effectively guide the development of new people. New students and other new students will inevitably appear in the project. It is an important task for the project manager to guide and train new people, don't count on your company to be a master!

2. Be honest

You must keep a normal heart at all times. You may encounter many problems in the project. Sometimes you may think about how to come to me, but you must understand that you are a project manager and everything in the project is related to you!

To be generous, the project team members will inevitably complain. You cannot just use your own resources or hear others' opinions. If you think that different opinions are challenging your own authority, others' ideas are not inferior to yours. You are also a project manager and not a great person.

3. Decisive handling

As a project manager, you must be decisive. If there are two possible ways to do things, you must define a method and never adopt an ambiguous approach, if you don't have a master, you don't even know what to do.

Do not expect all members of the project to develop standardized code. After all, you can take the project as your own project and do it conscientiously and responsibly, but not everyone else thinks so, and generally programmers have little idea about the whole world. The specifications here are not just development specifications. For example, many File Upload functions need to specify the file path, the directory structure for development, and the location of Common Code according to the functions ...... It is very important to start developing specifications. Otherwise, you will find development messy in the future.

4. Trust others

Maybe I am a person who prefers encoding, and I am always not at ease writing some key code to others. The best way is to instruct other people to compile the program. The project manager has a lot of chores and involves less time for management in the middle of the Code. The loss is worth the candle and will also impair the enthusiasm of others, code maintenance will take a lot of time in the future.

For a relatively large project, it is impossible to check every function. You can designate several major functions as group owners to motivate others.

5. Have certain architecture design capabilities

At present, this project is not fully designed and the demand is not very clear. Many domestic projects with tight schedule may have this problem. The design document is just a general framework. In the development process, we can only adopt a similar method of extreme development to gradually improve the functions. Therefore, it is inevitable to design again during the development process, including the design of the page layout. Generally, the artist only designs the page style, but for the page layout, the important information mentioned in "don't let me think" is placed in a prominent position, these things need to be re-designed constantly.

6. Arrange the time reasonably

Including arranging your own time and team time properly.

You should spend most of your time on project management and should not be stuck in a certain technical difficulty.

Meetings required for team management must be held, and meetings not required, such as regular meetings or so. If there is nothing to do, it will waste everyone's time.

There is no need to work overtime in a unified manner for overtime. For example, some people are coding their noon breaks, so they do not have to work overtime well after completing their tasks for the day. Work overtime is required if the task is not completed.

So far, the general requirements, demand change management, risk management, and Progress Management in project management are not written, which are embodied in specifications such as CMMs.