Comments on: A Tech Lead Manifesto http://www.magpiebrain.com/2006/09/12/a-tech-lead-manifesto/ The blog of Sam Newman Sun, 07 Mar 2010 21:59:36 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: nitin http://www.magpiebrain.com/2006/09/12/a-tech-lead-manifesto/comment-page-1/#comment-3258 nitin Wed, 08 Apr 2009 07:54:47 +0000 http://www.magpiebrain.com/blog/2006/09/12/a-tech-lead-manifesto/#comment-3258 Awesome article. I completely agree to whatever every one has commented earlier. However I have something to add to it - Knowledge sharing is the most important part of building and nurturing a team. Take necessary measures to avoid centralization of knowledge. Arranging frequent small technology sessions for team [Just-In-Time] will help to boost team's confident singificantly. Keeping the fact in mind that no one is 100% when it comes to technology however a healthy mindset and a positive attitude towards technical challenges will take a Tech Lead to places. Develop and motivate killer instict and clear focus on deliverables among team members. Another important aspect is a Agile is a shift of paradigm for them who comes from Waterfall model. So it's very much important that every one knows clearly about Agile before jumping and starting Agile practices. If your team is transitioning from Waterfall to Agile it makes sense to spread a word in the team about it. It's very important for a Tech Lead to come out of dictatorship and facilitate collaboration among team in order to succesfully perform in Agile. Come out of "ME" and work towards "US". Agile is all about team work, collaboration and not about any individual contributor. Awesome article. I completely agree to whatever every one has commented earlier.
However I have something to add to it -
Knowledge sharing is the most important part of building and nurturing a team. Take necessary measures to avoid centralization of knowledge.
Arranging frequent small technology sessions for team [Just-In-Time] will help to boost team’s confident singificantly.
Keeping the fact in mind that no one is 100% when it comes to technology however a healthy mindset and a positive attitude towards technical challenges will take a Tech Lead to places.
Develop and motivate killer instict and clear focus on deliverables among team members. Another important aspect is a Agile is a shift of paradigm for them who comes from Waterfall model. So it’s very much important that every one knows clearly about Agile before jumping and starting Agile practices. If your team is transitioning from Waterfall to Agile it makes sense to spread a word in the team about it.
It’s very important for a Tech Lead to come out of dictatorship and facilitate collaboration among team in order to succesfully perform in Agile. Come out of “ME” and work towards “US”.
Agile is all about team work, collaboration and not about any individual contributor.

]]> By: Steve van Bodegraven http://www.magpiebrain.com/2006/09/12/a-tech-lead-manifesto/comment-page-1/#comment-3256 Steve van Bodegraven Thu, 29 May 2008 23:45:16 +0000 http://www.magpiebrain.com/blog/2006/09/12/a-tech-lead-manifesto/#comment-3256 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. 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.

]]> By: non-random ramble :: Immersion Day3 http://www.magpiebrain.com/2006/09/12/a-tech-lead-manifesto/comment-page-1/#comment-3255 non-random ramble :: Immersion Day3 Fri, 14 Dec 2007 08:00:13 +0000 http://www.magpiebrain.com/blog/2006/09/12/a-tech-lead-manifesto/#comment-3255 [...] In particular, this entry From Sam Newman is relevant A Tech Lead Manifesto [...] [...] In particular, this entry From Sam Newman is relevant A Tech Lead Manifesto [...]

]]> By: vikas http://www.magpiebrain.com/2006/09/12/a-tech-lead-manifesto/comment-page-1/#comment-3254 vikas Tue, 21 Aug 2007 07:53:16 +0000 http://www.magpiebrain.com/blog/2006/09/12/a-tech-lead-manifesto/#comment-3254 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. 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.

]]> By: Guy http://www.magpiebrain.com/2006/09/12/a-tech-lead-manifesto/comment-page-1/#comment-3253 Guy Fri, 26 Jan 2007 08:52:44 +0000 http://www.magpiebrain.com/blog/2006/09/12/a-tech-lead-manifesto/#comment-3253 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 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

]]> By: Jeremy Miller http://www.magpiebrain.com/2006/09/12/a-tech-lead-manifesto/comment-page-1/#comment-3251 Jeremy Miller Sun, 07 Jan 2007 22:42:49 +0000 http://www.magpiebrain.com/blog/2006/09/12/a-tech-lead-manifesto/#comment-3251 Very well said. Very well said.

]]> By: Caroline http://www.magpiebrain.com/2006/09/12/a-tech-lead-manifesto/comment-page-1/#comment-3252 Caroline Sat, 23 Dec 2006 00:05:42 +0000 http://www.magpiebrain.com/blog/2006/09/12/a-tech-lead-manifesto/#comment-3252 A tech lead should also encourage the team when they are under pressure and working to meet a tight deadline. A tech lead should also encourage the team when they are under pressure and working to meet a tight deadline.

]]> By: Vishal Singh http://www.magpiebrain.com/2006/09/12/a-tech-lead-manifesto/comment-page-1/#comment-3250 Vishal Singh Tue, 12 Sep 2006 09:59:59 +0000 http://www.magpiebrain.com/blog/2006/09/12/a-tech-lead-manifesto/#comment-3250 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 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

]]>