Many people are complaining about not meeting a good team, but a good team can not appear out of thin air, first-class team can not rely on team members to work, as a leader, to have a workable plan, and firmly implement, the times to adjust

"Journey to the World" in the Tang's monk team after hardships, finally seek the Scriptures, the goal is clear, Division of labor reasonable for this team finally laid the foundation for success. Tang's monk from the beginning, for the team set the west to learn the goal, although experienced various setbacks and hardships, but the goal has never wavered. Wu empty Pathfinder, eight quit lead horse, Sand monk others easily may, several disciples shoulder the task of protecting the Tang priest. Although different personality, each have shortcomings, but the goal decomposition reasonable and members of the Division of labor, eventually through thick and thin, to obtain the canon.

The story of "Journey to the World" extends to the actual team technical management, but also for reference, the author of the CTO club members, Hubei province, a Network Technology Co., Ltd. Development Director Yang Bin, he combined with his many years of experience to talk about the "technical team's goal plan and task decomposition how to do." The following is the full text.

Two years ago, came to the same city guide network, compared to the coastal area, the company staff size is small, but in Hubei Xiangyang is the largest, the company's main information and 3D map, the development of nearly 30 people. As with many managers to the new company, I did not fully gain the trust of the company at the beginning, no real power, or even no clear position, many domestic companies have such problems, I believe that everyone is not strange.

At that time, the company faced a change in the direction of business, from information to provide a platform to fashionable e-commerce. The deadline requires the development department to provide an available business platform, and like many companies, this decision does not take into account the ability of the team to withstand. In the project confirmation session, the verbal designation is for me to guide the completion, but to accomplish this goal, there are several realistic questions:

• No real power, except technical guidance, no personnel transfer rights;
• Team members do not trust;
• Do not understand the ability of team members;
• Although the platform objectives have been established, but the specific details are many uncertainties, the project needs will be endless;
• Short task time (10 months);
• In the development of new products, the old platform still needs to maintain, but also to ensure that most of the column smooth transition.

Of course, I like this very challenging job, after a short review, I decided to start from two aspects: on the one hand, for the company to develop a 2-5-year department Building and Technology planning programme, through repeated exchanges, to obtain management approval, because only by their support can mobilize company resources; On the other hand, Take care of the programmer group in the development department. Because the product is finished, they are the main builders; The development department consists of three groups, the programmer group, the UI group, the test group, the programmer group is the dominant position in the department, the project can have the possibility of success only by obtaining their support; From the technology, the existing team leader opposition is less likely, management leader no objection , is a kind of success, some programmers are dissatisfied with the project management mode, each for the array, there is no clear assessment system, reflect the personal value.

It is easier to take care of the programmer group, actively participate in the programmer group Project discussion, in the discussion I put forward the following requirements.

1. To achieve the goal of the development of this e-commerce platform, the first thing to do is to have a good technical application framework, for which I set up a new framework, while writing a case to demonstrate, explain the application of technical points, this step, won the support of most especially the technical school programmer.
2. The new framework is more structured, the technology is more normative, but requires a high level of programmer ability, in order to reduce the concern, I wrote a code generation tool, to complete the workload of 80% code, and the rest of the more related to the specific business. Tasks become relatively easy due to tool help.
3. In order to ensure the success of the project, the current workflow must be changed, and according to the existing department and personnel characteristics, the development of a new workflow, and the process of the various types of work in conjunction with the timing and tasks undertaken.

Through a period of effort, the good side is that not surprisingly, the team of technical staff trust and respect, and understand the problems between the groups, through their own speeches and actual code capabilities of the existing programmers, UI staff, testers to classify, the bad thing is, still not get the implementation of power. We are still developing and arguing in the old way. It was just the Spring Festival, and the project was still small. But as time went on, the project was released more and more closely, and finally the company decided to let me take the overall responsibility for the development department. All efforts are worthwhile, early communication, communication, training to obtain the return, when the Department of Management, I quickly according to the ability of members to assign their own project tasks, and developed the development of operational norms. Although there were still bumps in the process, the project code was not exactly what I thought it would be, and the project task was completed at a specified time, exceeding the initial expectation of the project's effectiveness. Through this matter, I basically gain the trust of the company and the team.

The following year, the implementation of a new management model and development model, relatively smooth, but also to cultivate a group of executive management staff. Regardless of the size of the project, due to process standards, documentation, everyone is like a commando, whether it is a man-to-man combat, or a team attack, even if the team temporarily off, we can complete the task according to requirements and not from the chaos.

Like software design, there are many models, but does not mean that we have to follow these patterns to design, software team management is the same truth, we have a lot of management model for reference, no one is absolutely correct or wrong, "the uncertainty of the army, water impermanence shape", only understand the team, and handle the internal and external relations of the team , can achieve "curried", in order to reasonably assign tasks.

Unconventional, simple sharing under my experience, some management is can be inexpressible, the experience described above, hope to give you a little revelation.

1. Do not look at the project in isolation, the development team has to do not finish, change the bug, can not only focus on the present, to formulate a long-term feasible goal plan, preferably more than 2 years. First of all, the team will not be confused by the uncertainty of technology development, especially those high-tech developers are more so, easy to retain talent, second, the projects to evolve around long-term objectives, so that existing projects have greater marginal benefits.
2. Correctly handle the relationship between the superior and the same level departments, obtain the superior support is the premise, obtain the understanding of the same level department is the key to the project success. Senior High-level consideration, different departments concerned about the interests of different, can not only consider their own departments, to understand that the project is always in such or such problems (personnel, funds, resources, etc.) to complete, do not do perfectionist.
3. The development department is the producer of the product and is easily criticized when the project is in trouble. As a team of leader, to do a good job of communication and exchange, do not let the team directly affected by the negative, some problems arise very complex, can not be simply pushed to subordinates, to have the responsibility. After dealing with the problem to summarize, formulate an effective system (process, etc.), to prevent the next occurrence.
4. Avoid hands, trust subordinates, suspects do not use, employing not suspect, with clear published norms to assess subordinates, guidance and not to blame, draw the boundaries of responsibility, reward.
5. Improve various documents, in the project, some documents are required, such as:

• Requirements documentation, unclear requirements, can not start the project;
• Stakeholder table, clear responsibility, clear weight, is the key basis for the assessment;
• Code check-in specification, enhanced code auditing, which can improve product quality, but also improve the ability of participants.

Through a two-year team effort, despite the many problems, the same project, in terms of efficiency, was halved by half the time needed and the number of participants halved. Successful completion of the project, team members have a sense of accomplishment, and continue to grow, technology is constantly upgrading, more importantly, the company can achieve greater benefits.

Many people are complaining about not meeting a good team, but a good team can not appear out of thin air, first-class team can not rely on team members to work, as a leader, to have a workable plan, and firmly implement, the times to adjust, this is very critical.

http://kb.cnblogs.com/page/505877/

Many people are complaining about not meeting a good team, but a good team can not appear out of thin air, first-class team can not rely on team members to work, as a leader, to have a workable plan, and firmly implement, the times to adjust (go)