Technical Lead

A less pretentious term than ChiefArchitect. Or a more politically correct term than system architect - one that allows the role of architect to be carried out without ruffling so many feathers.

Being a technical lead requires balancing technical and leadership talents. A technical lead has to more than a good programmer. A real desire of working with people is needed. A very good checklist for what it means to be a good technical lead can be read here: http://littletutorials.com/2008/07/07/success-as-technical-lead/

Bastian Klaus

Our TechnicalLead doesn't do any designing, architecting, or even much coding. For that matter, most TechnicalLeads I've met here don't either.

Ours spends his time fiddling with requirements, GUI designs, meetings fighting with people over requirements, conducting interviews, talking with his boss about nothing useful, fiddling with new software that has nothing to do with ours, or looking at Yahoo! Finance.

I made him inspect some code a little while ago (I'm going with inspections because PairProgramming seems impossible here.. I know it's not a direct substitute, but it's the best I can do right now) which seems to have prompted him to take a Java Applications class.

I'm usually the one that processes requirements into stories, designs, schedules + assignments, or better code! or best.. rejection! I love rejecting requirements... especially when I've got a good reason. (TerminationCanBeSuccess)

It sounds like you're the actual TechnicalLead though you don't have the title.

I'm beginning to think that repeated visits to Yahoo! Finance during work hours is an AlarmBellBehavior for programmers (kind of like an AlarmBellPhrase for employers).

On the other hand, I know of "System Architects" in this company that do designs. Sadly, leads here seem to be working towards MBAs (away from code).

Yeah, to me this sounds more like either a ProductManager, DevelopmentManager? or TeamLead. Not that all of these roles couldn't be done well, but its pretty nasty to have TechnicalLeads and SystemArchitects that do no design!!! -- RobertDiFalco

Our TechnicalLead doesn't do any designing, architecting, or even much coding. For that matter, most TechnicalLeads? I've met here don't either.

Well, it's not like that here at NuMega. Our TechnicalLeads do 100% programming in addition to architectural design. In fact, they are totally responsible for a technical part of a system like the Java part or the Web Scripting part. They are a chief technical resource that people consult on their areas of expertise. Our DevelopmentLeads? do the managerial stuff.

-- sg

"100% programming in addition to architectural design": haven't you read Slack by TomDeMarco? ISBN 0-767907-69-8

I've been calling myself "TechnicalLead" for a while now. When I say it, I mean that I start programming in a better way, and people tend to see that it is working and find themselves drawn into working the same way. Then I start looking for the next better thing to do.

As I frequently tell my manager, nobody listens to me. They just DoAsiDo. When it is good, usually. On rare occasions they DoAsiDo in negative ways. This has taught me a lot about what it means to be a TechnicalLead. Sometimes, the most important part of the job title is simply recognizing that people will propagate your behavior if they respect you, so you should make your behavior the way you want other people to work.

Another important note: By being a technical lead in this way, and talking to people about it, I have helped other people on the team start moving toward being leads themselves. You can't necessarily teach leadership, but sometimes you can lead the way there!

-- JeffBay

moved here from ChiefArchitect

I really don't mind TechnicalLead at all though I do think it is one of those politically correct terms so people don't get upset about someone being called the architect. After all, if you did create or even facilitate the primary architecture of a system why shouldn't you be called the System Architect? In any case, I do think there is a substantial difference between TheCoach (or Team Lead) and the Architect (or TechnicalLead). For example, I don't think an architect has to be a good manager or that a manager needs to be a good architect. Many successful projects have a project manager that is distinct from the lead designer. So, with those caveats in mind, I think TechnicalLead is a fine term. -- RobertDiFalco

moved/reworked from TechnicalLeads

Original: All the senior levels like Technical Leads, project managers, project lead, Project coordinators, Project lead's, Archtect... etc., should be given and defined correct roles and responsibilities. Then they may start working with the team. Otherwise, they may think that being and conversing with other senior people is their job, trying to convince their seniors that their work is important. Other than that, they should be made to convince their subordinates. Then, all problems will be solved.

Proposed: All the senior levels like Technical Leads, project managers, project lead, Project coordinators, Project lead's, Archtect... etc., should be given and defined correct roles and responsibilities which must incorporate the notion of lead. The work is with the team, not being and conversing with other senior people, trying to convince them seniors that their work is important (see ImpressionManagement). They should concentrate on convincing their subordinates that they are leaders. Then, all problems will be solved.