technical lead
Dear all,
Could you give me some feedback on the following?
We are an organisation with about 12 scrum teams.
In each scrum team, one of the experienced developers
is a tech lead. He acts as a representative for the team
in architecture meetings, has the responsability to guide
less experienced developers and to preserves consistency
in the code base.
These are ofcourse valid points. However the Scrum guide
says 'Scrum recognizes no titles for Development Team members'.
What are your thoughts on this? Is this a recommended practice
or not? Do you have one or have experience with a comparable
situation? How to guarantee the points above, notably consistency
in code base, without one?
Best wishes Marc K
Is there a policy for gradually removing each team's dependencies on its tech lead, such as by disseminating particular knowledge and specialisms, and for other team members to champion those skills and represent the team accordingly? How would each team choose to self-organize in terms of taking on certain areas of expertise? Is this addressed in each team's Sprint Retrospective, and are action items for skills development and knowledge transfer planned into each team's Sprint Backlog?
Dear Mitchell,
Thanks for your questions. Helpfull questions when creating a path to remove the dependency on the tech lead. However right now the question is still open whether we continue with having a tech lead or not. So the question is currently are the pro points for a tech lead valid valid enough to keep one in place.
Best wishes
Marc K
Assuming it is desirable to have a self-organizing team, what impact could it have on the behaviour of the various team members, if one of them is appointed as the lead?
A few years ago, my Scrum Trainer in a ScrumAlliance course told us "the Tec Lead is the enemy of the Team" ;-)
Dealing a "tec lead" in the Dev Team is a nice challenge for the Scrum Master !
Hi all,
Thank you for the feedback! Helpfull info and I can continue with it, thanks.
Best wishes
Marc K