Hello, e.thrash, you wrote: ET> That should be at from qualities - to Help other participants of a command with organizational and technical questions (within limits time) - to Defend a position of a command or separate developers (if the developer really has to be helped) before the higher heads - Correctly to arrange tasks among members of team, depending on their abilities and loading - Correctly to define priorities of tasks - to Trust developers who have more than knowledge or experience in any specific areas not to press on them the - to Remember that Vasja can appear the rights - To be active enough (differently, even if is the strong programmer, it can be not the best applicant for a tim-lead position) - not to pull a blanket on itself to be able to delegate - to Care of creation of the necessary surrounding (, the monitoring system , build server (if is necessary) to pass to a new development environment to take care about different , To enter the useful experts (tests, for example, if suddenly they are not present) etc.) - to Care of transmission of knowledge. What if Vasja which are engaged of new releases is ill? Whether someone can replace it? Or, for example, Petja the first learned to generate in a fantastic way the code by means of templates (for example 4 in.NET) - let Petja holds presentation for a command. - to be able to encourage, encourage developers, and not just "Vasja why you the pancake spent the whole 2 hours for feature ?" . Whenever possible to try to set positive, valid atmosphere in a command, to smooth conflicts. - to build such atmosphere that developers really listened and heard each other, tried to understand other point of view; to explain, if you note that Vasja Petja - Vasju does not understand Petja, and; - to Conduct meetings, to prepare for them, in advance to think that it will be necessary to consider, be capable to remember or quickly to learn, who than is engaged, what main current problems should be considered. Thus on meeting correctly to arrange time not to spend all led out time if any developer starts to consider any minor problem tiresomely. - to understand that all people different and if it seems that the task can be made for a day, and Petja asks 2 days, and all as a result was taken three it can be normal. Especially, normally it seems that the task can be solved faster, than then it turns out in practice. - Questions at issue to solve a command, it is not possible if to solve, - above if there is such possibility and sense. - and on the contrary, sometimes it is not necessary to discuss too much and , and the solid decision of a tim-lead (if it is skilled enough, assured and ready to take) to put responsibility an end in discussion. - to recognize the errors - to Look more widely, to look ahead. What overall objectives of the project in 1-2 months? In half a year? What principal problems now? Generally, time you the new person on the project in the beginning hardly be more careful, you can not understand much; the first couple of months look narrowly more, ask questions. About the code personally I would not hasten yet is can be the murderer of time and conflicts.