15 June 2006
Great Mistakes in Technical Leadership
Posted by Mikhail Esteves under: Random Websites; Tips .
Perhaps the most difficult job to do on any software development project is that of Technical Lead. The Technical Lead has overall responsibility for all technical aspects of the project – design, code, technology selection, work assignment, scheduling and architecture are all within his purview. Positioned right at the border of the technical and managerial, they are the proverbial “meat in the sandwich.” This means that they have to be able to speak two languages – the high-level language of the project manager to whom they report, and the low-level technical language of their team. In effect, they’re the translator between the two dialects.
Observation suggests that there are not that many senior techies who have the skills and personal characteristics necessary to perform the Technical Lead role well. Of those I have seen attempt it, perhaps ten percent did a good job of it, twenty percent just got by, and the remaining seventy percent screwed it up. Therefore most of what I have learnt about being a good Technical Lead has been learnt by counter-example. Each time I see a Technical Lead doing something stupid, I make a mental note to avoid that same behavior or action when I am next in the Technical Lead role.
One Comment so far...
Anand Says:
17 June 2006 at 4:17 pm.
Hi Friend,
I understood that Project Lead should have Multiple Personality. He/She should change our mentality, actions, body language & etc based on the situation which we are in. It happens for everybody not only for Project Lead. But the situation & kind of script is different.
Thanks for your information on Technical Leadership.
