Tuesday, October 18, 2005

Who should be your team lead?

These are my assessments as I am no manager but based on when and why I felt comfortable with my lead. Here are some nine tips :


1. He should be some one with good communication skills, a good listener and sincere
to his work.

2. He should not be in the same grade level as you are.

3. He should be atleast two grades higher or 3 years senior if possible.

4. If a team constitutes of similar grade level developers, then make them individual
contributors and component leads. The project manager (or an architect) should take the
responsibility of being the team lead.

5. He should have some hands-on exposure to the related technology you are
implementing your solution in.

6. The job of a lead should never be collecting status and maintaing spreadsheets. He
will soon lose the respect of the team members.

7. One who could bring some real value.

8. One who is a good mediator and arbiter.

9. One who could become a manager anytime but is not interested in it.

3 comments:

Pablo Toledo said...

Hi Ashish!

your unknown spanish friend ;) is at last able to communicate with you.

I'm afraid that being my friend can be good at most times, but can bother you as I link you, so you may recieve some span. I hope you stats up cover for this, but if you see just problems with me linking you, let me know. I don't need to link you for you to be my unknown friend at sun ;)

Let me comment on it! btw, This is second time I try to comment.. let's see if it ends as nice as previous, I'll try my best :)

1. He should be some one with good communication skills, a good listener and sincere
to his work.


Someone without prejudices would be another way to say the same? What we use to call an open minded?

2. He should not be in the same grade level as you are.

From where I come from (VideoGames Industry), highly technical, technical experience is more important than technical studies. You can see a difference of salaries prices between HS and Graduate in VGames somewhere lost Here

3. He should be atleast two grades higher or 3 years senior if possible.

I would say He must be highly knowledgeable in the area where he is exercising the leading. But He doesn't have to know more than anyone else. For leading you must have prooved yourself before. And that is only attained with time!

4. If a team constitutes of similar grade level developers, then make them individual
contributors and component leads. The project manager (or an architect) should take the
responsibility of being the team lead.


Yup. I worked this way in a general team of 30+, ~10 programmers. So yes, it goes this way... Divide, and you'll win, they say, don't they? ;)


5. He should have some hands-on exposure to the related technology you are
implementing your solution in.


I think I commented on this before

6. The job of a lead should never be collecting status and maintaing spreadsheets. He
will soon lose the respect of the team members.


If I were to be lead again, my condition would be that only half my time is devoted to it, and I can keep on my engineering (that's what I like, I do leading in the absecence on someone better).

A Lead is to promote that everyone is involved in the project, everyone has a chance to speak up and be listened, and decisions are taken on a rational basis that is explained to the team as many times as they need it to understand it.


7. One who could bring some real value.

He better do. Cause he'll be doing the risky decissions. He's leading, he owns responsability!


8. One who is a good mediator and arbiter.

No! Not in my field! A Technical lead does in no way have human resource skills. That is handled in Video Games with one step over the lead, the producer. He is the one to care about the one coming 30m late every morning or the jelaous and power hungry conflicts that may develope. A Technical Lead SHOULD NOT handle that. (to my humble opinion, of course!, maybe because I don't easily have those skills... yet? :P)

9. One who could become a manager anytime but is not interested in it.

Not In Programming. Face It, if you're a coder, after 35 the market is too competitive with the young ones. This world goes fast, and what took you a life to learn, it is all processed and served at young generations for a fraction of the time you needed it. We can only go managing, or to big corporations where our job position is safer at certain age.

--------------------

Hey Ashish! THANKS for linking, feel free to contact me however you consider. I hope you can forgive my impulse to link you without noticing you O:-)

Pablo Toledo said...

Sorry about the spelling errors!
I Promise to do better next time!

ashish said...

I always considered a team lead different from the tech leads. Even though these two roles can be played by the same person. I agree as a tech lead you don't have to be a people person but as a team lead thats an added advantage, In most cases the most important one.