From a developer to a teamleader — an unexpected journey - Vitaly Sharovatov - Codemotion Milan 2016
•
0 recomendaciones•426 vistas
Sometimes a developer faces the question or even a tough choice — should I become a teamleader or a manager? I cannot answer this question for anyone, but I can tell others what experience I had. I’ve met two types of teamleaders in the industry — one that is more an architect and doesn’t manage estimates or prioritisation, but is just responsible for the architecture and the code quality; and the second one that does both management and architecture. The latter one is the most interesting one, and is the topic of the talk.
Recomendados
Recomendados
Más contenido relacionado
Destacado
Destacado (20)
Similar a From a developer to a teamleader — an unexpected journey - Vitaly Sharovatov - Codemotion Milan 2016
Similar a From a developer to a teamleader — an unexpected journey - Vitaly Sharovatov - Codemotion Milan 2016 (20)
Más de Codemotion
Más de Codemotion (20)
Último
Último (20)
From a developer to a teamleader — an unexpected journey - Vitaly Sharovatov - Codemotion Milan 2016
- 1. Developer -> Teamlead Unexpected journey
- 2. About me ✦ client-side since 2000 ✦ server-side as well ✦ team lead in 3 companies and now leading 11 developers
- 3. Should I? ✦ should I become a teamlead?
- 4. Everyone’s different ✦ don’t expect people to be like you ✦ explain this to others ✦ balance between goals and motivation ✦ find strengths and leverage them
- 5. You’re alone and not alone ✦ You are the team ✦ Team success is your success ✦ Your ass gets kicked
- 6. Uncertainty ✦ Humans are not robots ✦ Just not possible to control everything
- 7. Knowledge ✦ management != development ✦ how deep is the rabbit hole? ✦ must be productive even not knowing enough
- 8. Skills ✦ Empathy ✦ Will ✦ Strength ✦ where to learn?
- 9. Time ✦ you’re not a developer ✦ processes take time ✦ delegation ✦ interruptions ✦ crazy hours
- 10. Compromises ✦ intuitive prioritisation ✦ “less worst” rule ✦ effectiveness ✦ be prepared to fail
- 11. Politics ✦ multiple areas of pressure ✦ you get the “feedback” ✦ hard questions ✦ building trust
- 12. Demotivation ✦ I love coding but can’t any more ✦ not being able to improve quickly
- 13. Motivations ✦ challenge ✦ growth ✦ model
- 14. Wins ✦ happy people + great results (not necessarily have both) ✦ the team is great according to everyone in the company
- 15. Results ✦ 200 product features backlog gone ✦ daily releases ✦ atmosphere, people, transparency
- 17. Recap ✦ it’s very different role, not necessarily a step up ✦ lots of uncertainties, accepting it ✦ different process ✦ might be hard for certain personality types?