Agile Roles and Responsibilities: Technical Lead

please find http://itsadeliverything.com/agile-roles-and-responsibilities

I have been Technical Lead at a start-up company. But I am exploring what actually are the responsibilities of a Lead.

Technical Lead

Most organisations I’ve worked in have had a Technical Lead for each project.  Where the organisation hasn’t acknowledged this role I’ve suggested they do so. This person is one of the Developers but has additional responsibilities.  The key responsibilities of a Technical Lead are:·

• Agree the technical architecture and ensure the architectural integrity is maintained
• Ensure adherence to standards of best practice (e.g. source code control etc)
• Co-ordinate the team’s day-to-day technical activities
• Mentor the other technical staff

This role is similar to that of the Technical Coordinator from DSDM (2002).

***********************************************************************************************************

An effective technical lead is never happy with the status-quo, and is constantly looking for ways to increase the team's velocity. Some would equate this to the Lean Software Engineering phrase, "eliminate the muda." "Muda" roughly translates from Japanesse to English as "waste." 

One of the Comments to the post:

One thing to point out is that obstacles aren't always technical in nature. And that a good technical lead will identify (and often help to work through) these as well. Specifically, working through issues with your business counterparts - if their requirements are incomplete, unclear, etc. this can be one of the biggest "muda" creating parts of a project.

Code can be perfect, but a project will still fail if you don't meet your organization's need. Fostering relationships and communication across the IT/business line can be one of the best things you can do for your team.

source

************************************************************************************************************