Lin Rui mention the name, presumably programmers are not familiar with. In those days, and I was looking at his "high-quality C / C ++ programming" to write his first official project. However, have you noticed in the two books I'm sharp, he's a concept has undergone great changes, that is, on the technical requirements of the project manager:
in 2003, Lin Rui with "software engineering thinking" in said: "the project manager must understand the technology"; in 2005: preamble "IT enterprise project management problems, methods and tools," a book, the Lin Rui reflect the views of some of the old, whether for project managers to understand technology, he had a different opinion: "in fact, the project manager does not have to understand the technology."
So, what project managers need technical capacity? From the technical staff to the project manager, but also a thinking, what kind of change? In this article I talk about my experience, inappropriate please feel free to correct me.
There is a very learned man thinks to ask a big Zen Buddhism, Zen do not speak, just keep him tea, tea overflowed not stop. The man was surprised: "Master, the cup is full, fit in it!" Jackson smiled, stopped hand, meaningful, said to him: "Yes, your mind is like the cup is full, I tell you saying, how can we pretend to be under it? "
Buddha said," knowledge barrier ", that is to learn a lot of things, but these things hinder their practice. Project managers, too, if too much dedication technically, but will hinder upgrade their management skills.
Then the project manager profession has what characteristic? Let's thinking and execution of two terms.
Let me talk about ideas: the
technician has two characteristics, namely, attention to detail, the pursuit of the perfect thing to do; Second, strong hands, often like to do things like hands-on. For project managers, these two characteristics are bad things.
Any person, any company, as long as things do make mistakes, as a manager, if bent on every detail to be perfect, it may in the end is nothing. For details of the improvements, I prefer the approach is to seize the most important thing (is generally directly related to the node QCD), these critical points must meet the requirements, the rest of the things you do not need to pull up too. Also, if the crew found down in the details of the local effort well done, must be timely praise. -In recognition, wider than commendable, is the best attitude to detail.
As a manager, team performance is your performance, but the team's ability is not equal to your personal ability. Maybe your technology is very strong, but it can not do anything myself, just like football, one team is not possible to achieve good results. Therefore, we must dare to put things other people do, maybe he has not done so well, then tell him how to improve, if not always do the same thing, then maybe the team members need for a more suitable job.
All in all, as a project manager, you are no longer doing their job, doing more of the work of others. Attention and leadership at all levels, business, technology, communication, attention to the state of QCD project, focusing on the overall situation, not the person, this is the project manager's way of thinking.
Talk about implementation:
a friend mentioned when talking of their company, a department manager trainee manager has told: "If you want good managers do that you must first learn how bonuses?!" Way, everything, and I favorite is the feeling of getting rewards ......
as a project manager, how to report, how to clear itself of responsibility and authority, is critical. The bonus is only one aspect, truly execute many more.
Reporting, you must first learn to e-mail. When reporting, mail sent to your leadership, copied to the relevant personnel; in the organization of work, the message is sent to the intended recipient, copied to the relevant leadership. Do not underestimate the message, it is important to support the work content, it is also clearly demonstrated the responsibility of everyone. Telephone, interviews, meetings and other means of communication, will eventually be confirmed in writing, and Mail, is the best confirmation in writing. Make good use of e-mail, make your work more orderly.
Authority and responsibility are closely related. You will be responsible for the appointment of a project manager from accepting the moment of QCD this project, but this is a generalization of responsibility, most companies will not directly given control over the resources of project managers, fees, etc., these resources may grasp the hands of the boss. Project managers need to report timely progress of the project and propose a plan for further work, as well as budgetary requirements, and then approved by the superiors who, approved costs. Good project managers and corporate executives to maintain good communication and trust, so as to obtain the necessary resources to promote the project.
As project manager, on the one hand to grasp the key nodes of a good project, on the other hand is accurate, timely and reasonable reporting, in order to fully enjoy the confidence of the leadership in order to obtain the necessary resources to promote the project, given itself the appropriate authority, which It is the project manager's work.
From the details to the global, from itself to the team, managers and technical staff from the way of thinking to the working methods are essentially different, that's what managers actually do not need to be technical reasons for cattle.
Back to the beginning of this issue, I think, is not a skilled project manager is not important, the key is to not let the technology "drag" his own, only go beyond technology, thinking in the overall project level, project management can really put off into practice; from another perspective, under the premise of a good grasp of the overall work, the project manager, appropriate to do some technical work, but also a very good team morale driving it!
Note: QCD which are quality, cost and schedule, are the three key project management, ability to grasp the QCD sign the maturity of an organization's project management.
Original: https: //blog.csdn.net/fzd999/article/details/1204155