A Tech Lead Manifesto
h3. Overview
I’ve had a chance over the last few years to observe various different types of tech leads. Collated here are my views on what I think makes a successful one.
h3. A Tech Lead Should…
* Ensure the creation of a *clear and consistent technical vision* for the project which can best result in a *successful project*
* Ensure all members of the *team* have a *proper understanding* of the technical vision
* Ensure that the technical vision *updates* to reflect *new requirements*
* Track and *resolve issues* where the *code deviates* from the technical vision
* Create an *environment in which all members of the team can contribute* towards the technical vision
* Understand and *address skills gaps* in the team which would result in difficulties implementing the technical vision
h3. A Tech Lead Should Not…
* Tell everyone what to do
* Necessarily be the best at everything
* Write no code
* Write all the hard code
Category: Agile, General 7 comments »
September 12th, 2006 at 10:59 am
Tech Lead Should
1. Mentor people.
2. Also understand that other developers in due course may become better than tech lead in technology as well as domain
December 23rd, 2006 at 1:05 am
A tech lead should also encourage the team when they are under pressure and working to meet a tight deadline.
January 7th, 2007 at 11:42 pm
Very well said.
January 26th, 2007 at 9:52 am
Hello
I have a question about the title: tech lead.
Is it just another name for “system architect” ? is there a clear difference between the two ?
Will apriciate if you can shed some light on this issue.
Thank you
Guy
August 21st, 2007 at 8:53 am
Tech lead should be the leader of the technology not the team.
any minor/major issues raised by team members, TeachLead should be able to resolve.
December 14th, 2007 at 9:00 am
[…] In particular, this entry From Sam Newman is relevant A Tech Lead Manifesto […]
May 30th, 2008 at 12:45 am
A nice summary…
Just one question on the response from Vishal Singh; what is the right way to lead a person who has become better than the technical lead in technology or domain (or aspect of the domain)?
We do not want to restrict or curtail their ability, but we need to ensure they are working toward the right outcome. I guess, knowledge transfer back to the technical lead (and other members of the team), technical reviews and continually highlighting the technical vision become necessary?
Should the technical lead change mid-project?
- Steve.