2015-7-8 12:15
is a pure spit groove, not for anyone and things.
For some three-stream teams, it's a bit more lethal than technically inadequate. is excessive process, process, meetings, meetings, analysis, analysis .... Repeatedly.... Did not enter the theme, in fact boss wants very simple, I want what you quickly give me
It's done.
OK, time passed, Opportunity missed, competitor's product on-line .... We just started coding. Such a process will only exist in large internet companies, and for three-stream teams in third-tier cities, the need is a doer,
Rather than analysts.
If you are a team of Teamleader, then receive the boos release of product development tasks, how will you assign? Here are two types of people to consider:
1, do not know the technology, but simply do leader people, let's call the project manager, directly lead the programmer, for the programmer to release production orders, and then timed to urge the live, the programmer how to do whatever, as long as the results.
2, know the technology, but also is the technical type leader person, has many years technical work experience transformation research and development type leader post.
2 different results:
1, the first according to the factory-type production process, has not been detailed design. This is the leader of the task assignment, the zodiac of those jobs, the lack of targeted assignments. Because they can't keep an overview of the team, even who is good at doing
What is not measured in the heart, often the result is too dependent on the results of the programmer, for the product quality, performance has no hard indicators, the consequences can be imagined, changed and changed, changed again and again this project began to become disorganized, messy
The code is flooded with the whole project, and finally it's not going to go down, refactor it! or abandon the project. In this kind of work, leader completely unable to grasp the programmer's movement, knowing that the programmer can not know what the end of the day to do, do not do a good job can not test
This is a very serious problem. If you want to solve this kind of problem, then this type leader must arrange a technical good vice leader for oneself, so as to advise oneself.
2, very fortunate, if the company team leader is the second kind of person then the company must be a potential stock, at least to let the program ape see some hope. Before the product task is released, the technical leader will carry on the project design according to the demand, the technical sub-
Design, and then according to the team each developer's technical strengths are different division of labor, and then plan a reasonable time, and personally participate in the project some core module development. As it turns out, the team will certainly do a very
Products, and team communication will be more harmonious.
Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.
Talk about the three-stream team.----(2) Tasks under Boss Assignment