About the complement of the repairman
Yesterday, I looked at the "Master Car Master = Software Project Manager" and discussed myself.
Make the fox: Management is a few levels, each level needs to be managed. For example, high-level leadership management, departmental managers have managed by all projects and departmental development of the department, and the project manager is managed by the project. As for the lowermost soldier, it is necessary to have an effective management of their own tasks.
I very much agree with him, but for us, the high-level management has not been touched. I don't dare to comment, I can only talk about software project management that is close to the specific development work.
Linghu said: This is an example of a typical management. The repairman should do it. Tell the apprentice how to repair the car (basic knowledge training), and must also tell them how to reasonably arrange their work (management knowledge Training), the master should also be properly intervened, do some high-level arrangements (project management) for the apprentices, so that this team can effectively operate the apprentice to learn, the master must learn, the master's professional skills should be no problem, Then he should learn how to reasonably use resources in your hands, including static resources and human resources.
This is also what I want to express: technical experts may not be managed experts, although it can be gradually mastered by learning, but this is not good. The long and avoiding weakness is a better way to use people. If a company, only the only promotion of the development of the management, it will inevitably force the technician to abandon the long, and it is short. Just like let Anders go to the CEO of Borland.
On the other hand, technical management must also understand technology, and participate in it, although he doesn't have to be a master, but it cannot be separated from technology. In fact, in the MS, many project managers and even senior product supervisors are doing coding work, but the domestic software project manager seems to be a high-rise, I feel that the high people will be able to do it again. Come to them more than MS's primary products.
Linghu also said: According to agile requirements, the manager itself is also participating in the development, but his mission is more heavy. He plays more a role of coordination team, not a polar role, as a team The manager should be the opening of the statement, and the control spoke topic will not deviate from the person who is too far away, not a long-term big interlace in the case, so that other participants can only accept the person.
I agree with this point, there is a saying: If there is only one person at the meeting, it is not a meeting, it is class.
Of course, the class is also necessary, that is, the mutual training between members. Linghu mentioned a training method that does not affect the work is to establish the company's internal knowledge base. This is a good way, but I want to face the face to face the same is ordered, but I can only work in the work of voluntary principle, so The words must ensure that XP requires 40 hours a week, cannot work overtime. This is more difficult.
This article quizes the opinion of the fox, and he first damages. ^ _ ^
