Items to be avoided in project management

Project management is an art. Some people are good at project management, while others can master project management skills through hard work. Some people cannot master the secrets of project management in any way.

 

The following lists some items that should be avoided in project management.

 

1. All trivial matters are respectful

New members in the Project Group need to install machines, software, and development environments. as project managers, they should not install these items for everyone. There are two solutions:

A. Write document specifications. Everyone can install the environment according to this document;

B. Teach a person how to install the environment and ask him to help others install the environment.

From this point of view, it seems that it violates the principle of "serving others. However, when "services" need to serve electronic services, only your "services" can help others solve problems and make their work continue to advance, such a "service" is what you should provide.

 

2. frequently ask team members about the progress

The frequency here is also a relative concept, generally twice a week, or several times a day at a critical point. However, you can ask the team members about the progress every other time (maybe one or two hours or ten minutes), which may affect the efficiency of the team members, on the other hand, it puts pressure on team members. Trust team members and ask them to seek help or ask questions when they encounter problems, even if they do not ask about their work progress, you can still observe the progress and progress of your work from the question they asked.

 

3. Swing left and right

As a project manager, you must be able to make decisions within your own scope. For a project, some people support solution a and some people support solution B. So you should have a focus in your mind. Maybe you don't need to make a shot, but you must be aware of it. You can put forward your own unique opinions when it is critical. If you are afraid that after the supporter of solution a brainwashed with you, you will say "Good, solution a". After the supporter of solution B brainwashed with you, you will say "Good, solution B ". Therefore, you have never been a master. Follow the ideas of the two groups and you will be B for a while. Of course, the premise is that you have a sufficient understanding of the project.

 

4. Zoom in

What should you do and what should you not do? You must be clear about the core technology, the progress, and the working status of everyone. What are the difficulties ...... If you don't care about these things, you can do other things, such as "Let's see who is late for work today and who has worked most overtime this month, let's see who is married and there is no wedding candy ......". If you do not do the same thing as the latter, you are more and more concerned about the latter.

 

5. Always say "I'm busy"

Who does not work overtime as an IT employee? Who is not busy? Who is not tired? Instead of being a manager, you can stress your work to the people at the bottom of your hand. Instead, you can easily do some work, such as organizing the animation formats of the PPT. I always use my busy schedule as an excuse to let people in the bottom of my hand do what I should do. Instead, we should take the initiative to undertake some key core tasks, which greatly improves the Team's work efficiency while providing core services.

 

6. strict self-discipline, wide self-discipline

Most software projects will be postponed. Since they will be postponed, what is the role of the project plan? The purpose of a project plan is to provide guidance in order to follow the plan. However, a project may encounter various risks. Therefore, when assigning tasks to each person and setting task time points, factors such as personal abilities and difficulty of tasks should be considered comprehensively. Do not always assign a tight time node to the project members (although it has a certain degree of supervision), but it is best to arrange a reasonable time node and leave a proper margin. As a project manager, when assigning tasks to project team members, it always requires a tight schedule and does not require them to modify the time node (even if it is clearly felt that it could not be completed within the specified time point ); however, when assigning tasks to yourself, there is always a long margin of time.

 

7. Do not do what you want

Project Team members are only around (physically) project managers. Some people make loud calls, while others make great voices when discussing issues with each other. Their voices are actually related to the company culture, if everyone speaks very low, I believe that anyone who just arrived at the company will be able to speak in a low voice. However, as a manager, he often calls and speaks a lot. Instead, he asks the project members to speak in a low voice, which is too much.

 

8. steal others' results

Clearly this document was written by a project member, but as a project manager, it was changed to its own name;

It is clear that this task was accomplished by a project member, but the project manager did not mention the name of the project member when reporting to the superior;

It took several weeks to solve a problem. As a project manager, I said, "Actually, I will do it ". Why have you been there?

 

9. Instruct team members with commands from superiors

In fact, the superior did not give any command or instructions, but the project manager said, "*** leaders let you do it ***", which is shameful.

 

10. pseudo Resource Manager

A key task of a project manager is to manage resources and promote projects through management and utilization of various resources. Problems and risks may occur during the project. When a project member encounters a problem that requires a high-rise project manager to solve a technical problem or solve a problem, the project manager says, "I will contact you ***", or you can find it ***". Of course, you can always find the right person to solve the problem, which is also a kind of resource management capability. However, there are always various problems in the face of some resources that you cannot directly allocate. In addition, if every time you say "you look for *** and you contact ***", what can you do? Is it an empty shell?

 

11. Taking overtime as a work attitude

It doesn't matter if you work overtime, but it's too much to take overtime as a measure of the quality of work for project members.

 

12. Depending on money as life

Team members need to apply for a machine and say they want to use it for testing. The project manager says "It's expensive. Let's borrow it from someone else", or "you don't know how tight the project budget is, you don't know the pressure on my seat ". The project team members had a meal and paid 200 or 300 yuan for the first time to reimburse the company. The project manager said, "Why did you eat again ?" What is wrong when I apply for a machine for a project and dinner for team building?

 

13. view the commands of leaders as military orders

It is true to obey the leadership command, but it is too bad. For example, the senior leader said that it would take three months for new R & D personnel to go to the engineering department for an internship. As a project manager, new employees were originally employed to alleviate the contradiction of insufficient manpower. As a result, they first sent an internship for three months in another department, regardless of the pressure on other team members.

 

14. Be clever

One day everyone is traveling, and everyone has exchanged foreign currency A and foreign currency B. When they come back, the manager goes to the bank to exchange the remaining foreign currency A into the renminbi, but does not exchange the remaining foreign currency B, instead, exchange foreign currency B with team members in RMB. The team members thought that the exchange rate between foreign currency B and the renminbi had fallen.

 

15. Pseudo-Representation

When I took a nap at noon, I suddenly heard a major leader in the aisle lead other people to visit the company. The manager immediately woke up and tapped the keyboard with a loud voice to let the leaders know, he is working hard ".

 

16. Be a good man

I am always a good guy in front of others (people outside the project team), so I can make the people in my project team alive.

 

17. Good luck

A project member proposed to carry out study and training activities in the project team, and then the project manager sent an email to the group saying "We encourage everyone to carry out training activities. I will take the lead in this activity ".

 

18. Ripple

Play articles on emails

 

19. Caring for superiors is better than caring for subordinates

 

See if you are doing well enough?

To be continued...

 

[Not reproduced without the permission of the author]