In 30 seconds
- Supports a self-managing team rather than assigning tasks.
- Often focuses on technical guidance and people growth.
- Not a Scrum role, but common in practice.
Typical responsibilities
- Technical guidance and standards
- Growing team members' skills
- Removing obstacles alongside the Scrum Master
- Representing the team with stakeholders
Fitting with Scrum
Scrum has no team lead role; responsibilities are shared among the Developers, Product Owner and Scrum Master. Many organizations still have team leads. The key is avoiding overlap and confusion, such as a lead assigning work that the team should pull.
Leading without commanding
Ask questions before giving answers, let the team decide how to do the work, and lead by example in code and behaviour. See servant leadership and self-managing teams.
Myth vs reality
Myth · A team lead is the boss.
Reality · In agile, the lead supports and guides.
Myth · Team leads can't exist in Scrum.
Reality · They can, with roles clearly agreed.
Myth · The lead must be the best developer.
Reality · Leadership skill matters as much as technical skill.
FAQ
Is a team lead the same as a Scrum Master?
No; the Scrum Master focuses on process and team effectiveness.
Should the lead do performance reviews?
Organizations vary; keep it separate from daily work allocation.
Can a team lead also code?
Yes, most do.