What are the qualities necessary for an excellent Internet Project manager?

The project manager's job is to plan versions and budgets, coordinate various internal and external resources, and ensure project progress and quality. Excellent project managers need to do a good job from the above several aspects, summed up there are three key points : System planning, target-driven, risk awareness.

650) this.width=650; "src=" Http://img.mp.itc.cn/upload/20160415/ad03b06d6bf941abaeb0e80b10221940_th.jpg "style=" border:0px;margin:0px;padding:0px;font-size:0px; "alt=" ad03b06d6bf941abaeb0e80b10221940_th.jpg "/>

　　One, System planning

　　The so-called system planning is that we are involved in the overall project development of funds, time, personnel, etc. have a deep understanding of the knowledge and adequate preparation work. Many of these experiences are dependent on the project manager's own sedimentation and their data accumulation. This is also the fundamental factor of the success of the project!

　　The first thing to do in the management of a project is systematic analysis and planning, considering the feasibility: the technology is not difficult, the money is enough, the time is tight, the programmer is not reliable, the key problem is the main contradiction. Then make a reasonable, executable plan.

　　For example: The biggest problem with a project is often the boss's blueprint is too ambitious. Project managers need to grasp the main contradiction and envision how to simplify their grand blueprint tothe rest of the "1.0 version". Given the staffing level, the project manager should be aware that for a simplified, uncomplicated version, your programmer might be able to do more. The details that programmers don't need to know are not written into demand.

　　In short, the success of the project is influenced by many factors, and each factor also affects each other. The project manager needs to be able to clearly recognize the elements that affect the success of the project and the relationships and contradictions between them. Then straighten things out, then break down the goals and step into it.

can't grasp the focus boss

　　wrong expectations. . There is no correct understanding of the responsibilities of the specific members, there are erroneous expectations, for example: Performance in the product manager demanding inspection delivery visual effects. Product Prototyping stage do not expect the interface to look good, unless it is ugly grievances, as long as the function is available, it can be accepted. It's like repairing a house, painting and decorating is the last job.

650) this.width=650; "src=" Http://img.mp.itc.cn/upload/20160415/aded5d102e324af190b7138841676d33_th.jpg "style=" border:0px;margin:0px;padding:0px;font-size:0px; "alt=" aded5d102e324af190b7138841676d33_th.jpg "/>

　　Two, target-driven

　　The goal-driven focus is on our work to be guided by the results of the goal. Many problems we can not only focus on the right and wrong, but should pay more attention to the results, not only to find evidence to put out the problem, but to take the initiative to solve the problem.

before in the programmer's Inn there was this one development project case: a dispute between the enterprise and the programmer, the main problem is that the programmer does not have a high-fidelity restore UI design, There are other problems, of course. Then it started to get noisy and began to rip. ... and then they all wrote more than 10 pages of word documents, charges are the other side of the problem and start applying to the Programmer's Inn for arbitration. If the project manager encounters such a problem, it should solve the positive problem, rather than join the queue to find evidence, win or lose.

　　Goal-driven we can also be divided into executive power, quantitative management, communication skills to talk about.

　　1. Executive Power

　　solve the problem of system planning, the next step is to set up a team to work according to plan. Imagine a scenario where everyone's tasks are not completed, the meeting is not ready, procrastination is done, and a week goes by, and you find a programmer who says his job is at risk, and he tells you not to worry about it.

　　The above phenomena are the weak performance of team execution.

　　all the execution of the problem, in the case of good money, should be first from the spiritual level to solve. Procrastination, poor sense of responsibility, weak sense of purpose ... all of this is the cause of the problem. so to work at the human level, the team members do not understand the familiar to understand, to gradually let the programmer take responsibility, and strive to quickly embark on the development of formal. In short, for the group of individuals at least to have a contractual spirit, or you can substitute.

　　Why do people listen to the conductor and do things actively? In addition to money, the previous work arrangement problem. Good at competent work arrangements, not disorderly command blind planning. Easy to be strong, easy to make work, easy to know is clear, is the rule of the birth also.

　　So the lack of executive power is also a matter for project managers to take into account. A good project manager is like an engine that leads the entire team to indomitable.

　　2. Quantitative Management

　　This Part I summed up three key words: "Clear division of labor" "Clear planning" "Inspection work".

view There was no check-up, or a delay in checking the time, the past a long time suddenly remembered to go to see this function do not have this is prone to problems of practice.

　　In short, to help everyone's work plan to the fine place. An individual who executes the development does not need to think too far, he should know exactly what he should do this day, and what will be roughly one months from now. The project manager needs to know exactly what each person does every week, and plan to run through the project cycle, one eye to the end. If a programmer does not work on this day, how do you believe his goal will be completed in a week? How do you expect him to give you a one-month post-crotch Haikou target? The so-called empty talk endangers, hard work hing bang. Talk about strategy and let the CEO and his investors do it.

　　If a programmer does not plan, the plan does not follow the planning, these are very dangerous signals, to be corrected in time.

　　In essence, as a team leader, if a project manager himself planning unclear, responsibility is unclear, all do not according to their own planning to move forward, grasping "clear division of labor" "Clear planning" "Check work" the key points, then do not think the programmer can enter the state. Anyone who is a person, spells and rewards and punishments, although no words and potential autonomy, unknown spells and rewards and punishments do not need to, although the day command, but the trend from chaos. Look at the project manager's work to see the chaos within the team.

　　Examples of related failure phenomena:

　　Poor management ability of project manager. Ren to enable so the relief, performance in the appointment of the talent too interference, the use of the capable person and fully delegated. For example: The daily painting of their own prototype to rob the product manager's life to increase communication costs. Do not change put the put, should not grasp the catch. Things that should not be delegated are delegated again, not to check the work. Planning does not fall into thin places, planning the implementation is not down. This is all a way of disrupting the war. I'm tired of being a loser.

　　3. Communication skills

　　The fundamental of communication is a negotiable way of doing things, a kind of thinking that stands in the perspective of others. All things, is self-the person of the shun, the release of the people to teach the inverse. The project manager's working methods should not be command, command, arbitrary. And should be negotiated, co-ordination, and constantly improve from their own. A plan to negotiate, a meeting to negotiate, a lot of people to discuss the affairs. Let everyone unite around you and move around the goal.

650) this.width=650; "src=" Http://img.mp.itc.cn/upload/20160415/5fb0299b08454977a9b4674a0a624595_th.jpg "style=" border:0px;margin:0px;padding:0px;font-size:0px; "alt=" 5fb0299b08454977a9b4674a0a624595_th.jpg "/>

　　Third, risk awareness

　　In the process of project management, there are too many accidents. If a project manager lacks risk awareness, he will continue to fall into the difficulties of failure of various risk-impaired projects. Performance in the form, that is, the project manager constantly in the handling of disputes, team Slack quarrel, constantly in to everyone wipe the buttocks, a day exhausted the project or problems. Basically this is the project manager's own level of problems.

　　WINS can be unknowable, long-term victories must be based on the constant elimination of the risk of failure. The most skillful doctor will cure the disease when it is invisible. Bad doctors only wait for the disease to get big, they will cure, still cure not good.

　　Project managers have high risk awareness, and through the accumulation of experience to identify the key risks of the project management, the project should not fail. Excellent project managers have a very deep sense of risk, the project in their hands in a well-organized, complex but not in a hurry, can be a variety of problems from the ex-post recovery to pre-prevention status.

This article is from the "Programmer's Caprice" blog, please be sure to keep this source http://cxykz.blog.51cto.com/11696626/1789118

What are the qualities necessary for an excellent Internet Project manager?