Technical Team Leader…Who Is Not

By | April 24, 2009

image orginially was on ""

When I started this blog my goal was to make it a technical one, in which most posts would have code, samples, screen shots, architecture…etc. This was the primary goal, though it is totally fine with me to talk about software life in general.

The issue is that I get the ideas of my posts from my real daily life, which is mostly code challenges at work. I do write code in my leisure time, but for sure it is not as thorough as the thing at work.
And since I haven’t posted any technical stuff lately…the simple conclusion is I DON’T SEE CODE ANYMORE!

A Technical Team Leader in the place I work at right now has a different meaning from what I knew before; the first word in the title is “Technical” so I expect to deal a lot with code: planning it, reviewing it, discuss it with team members…etc.
But in the environment I work at, there is more pressure toward management and coordination; I find my self during the day doing stuff like updating the Microsoft Project plan, smoke testing, running between other teams we depend on to get their deliverables; checking with the User Experience team if they have the designs ready, checking with the Architecture team if they will pass by to set the folders structure for us…etc. All this leaves me no time to see code.

Is this right? Should a Technical Team Leader do these stuff? If not, who should? Is it a Project Coordinator? what is exactly the job description for a Technical Team Leader?
Questions like these should be discussed with the Development Process people, but till then I will have to say: “that’s not right”.
How about you? what do you think?

3 thoughts on “Technical Team Leader…Who Is Not

  1. Omar Hattab

    I don’t know what to say, I agree that this not right, the technical team leader should deal more with technical stuff, but I disagree that you shouldn’t do what you are doing right now.
    So, until to get your exact job description, keep running you “Non-Technical” Team Leader. 🙂

  2. Emad Alashi Post author

    You are not disagreeing with me, because I am already doing it fully 😉 sighs though 🙂

  3. Maram

    Since I’am going through the same situation here “except the title where I work is Solution Designer”, I can say that this depends on life of the project. At initial stages you have to do all design issues, stablishing technical base for the project and the team. Toward the end this should turn into managing deliverables and providing less support to the team – since things would became piece of cake for developers then.
    On the other hand, just today – we where talking that TTL or SD is not much different from SSE!!! you keep writing code and not doing designing!!! So it is not PM and not Designing :S I really wonder what is it!!!

Leave a Reply

Your email address will not be published. Required fields are marked *