Do You Need a Software Team Leader?

30% discount for my eBook:
http://leanpub.com/memoirs-of-a-software-team-leader/c/DoYouNeed

Do you think that your team or company could benefit from introducing a software team leader position? If you think so, you may be right. If you don't... Well, you may be right, either.

The truth is, there's no simple answer. It depends much on what you work on and who you work with.

In my presentation I'll try to show when you'd benefit from hiring or designating a team leader and when it would be nothing more than a waste of resources. I hope that thanks to my talk it will be easier for you to make a decision.

Transcript

1. Do You Need a
   Software Team Leader?
   Łukasz Wróbel
   

   View Slide

2. About me
   ●
   Architect;
   ●
   team leader;
   ●
   high-traffic websites:
   ○ nk.pl;
   ○ Gadu-Gadu.
   ●
   author:
   “Memoirs of a Software Team Leader”.
   

   View Slide

3. Getting in touch
   lukaszwrobel.pl
   @lukaszwrobel
   

   View Slide

4. Agenda
   1. Trying to answer the question.
   2. What can a leader help with?
   3. The cons of hiring a leader.
   4. The second approach.
   

   View Slide

5. View Slide

6. 1. Trying to answer the
   question.
   

   View Slide

7. So, do you need a leader?
   

   View Slide

8. The most honest and concise answer is:
   I don’t know
   

   View Slide

9. Because I don’t know you.
   ?
   ?
   ? ? ?
   

   View Slide

10. A more detailed answer would be a bit fuzzy:
    It depends
    

    View Slide

11. ●
    What do you work on?
    ●
    Who do you work with?
    ●
    What do you want to achieve?
    Clues rather than answers.
    

    View Slide

12. 2. What can a leader help
    with?
    

    View Slide

13. Strict requirements
    

    View Slide

14. ●
    Quality;
    ●
    efficiency;
    ●
    scalability;
    ●
    security;
    ●
    …
    

    View Slide

15. Leadership should stem from experience.
    Experience is one of the ways of building
    authority.
    

    View Slide

16. Coherent vision
    

    View Slide

17. Everyone should participate, but…
    Subjective distortion.
    Democracy.
    Projection.
    

    View Slide

18. How good bad are the team
    members?
    

    View Slide

19. Maturity, responsibility.
    It’s good to learn those.
    Some people need to be taught.
    Some can be shaped.
    Setting a good example.
    

    View Slide

20. Facilitation
    

    View Slide

21. ●
    Discussion;
    ●
    knowledge exchange;
    ●
    moderation;
    ●
    mediation.
    

    View Slide

22. Leader can reduce costs.
    

    View Slide

23. Salary
    ●
    Mediocre developer: x
    ●
    Good developer: 1.5x
    ●
    Team leader: 2x
    

    View Slide

24. 6x + 2x < 6 * 1.5x
    8x < 9x
    Even if leader doesn’t do anything besides making
    the team work.
    

    View Slide

25. Team growth may be tempting, but:
    ●
    Overgrowth;
    ●
    communication overhead;
    ●
    effective coordination.
    

    View Slide

26. Five good developers together = not
    necessarily a good idea:
    ●
    Quarrelling a lot.
    ●
    Each of them may be right.
    ●
    Either democratic or effective.
    

    View Slide

27. Recruitment.
    Developers are in demand these days.
    A blend.
    

    View Slide

28. ●
    Avoiding problems to come;
    ●
    expandability;
    ●
    maintainability;
    ●
    monitorability;
    ●
    …
    

    View Slide

29. 3. The cons of hiring a leader.
    

    View Slide

30. Trust or protection?
    

    View Slide

31. ●
    Self-organization?
    ●
    Achieving maturity?
    ●
    Self-confidence?
    Not what a Scrum Master should do!
    Protection
    

    View Slide

32. Building trust.
    Customer, other teams.
    A long-term process.
    “I don’t like it, but I believe you.”
    Trust
    

    View Slide

33. A firm hand
    

    View Slide

34. ●
    No room for discussion;
    ●
    here is the decision;
    ●
    it should take you this amount of time;
    ●
    lack of knowledge transfer.
    

    View Slide

35. My precious
    

    View Slide

36. I’ve got the power.
    And a sieve.
    Seems interesting?
    I’ll take care of it.
    Here are the leftovers.
    

    View Slide

37. Favoritism
    

    View Slide

38. I like you more, so…
    I have the power, remember?
    Not a robot, but:
    ●
    Correct: judging by skills, attitude,
    experience.
    ●
    Wrong: matters of personal concern.
    

    View Slide

39. It already works
    

    View Slide

40. Self-organizing team.
    Why should anything be changed?
    Change for change’s sake might be a good idea,
    though.
    Room for improvement?
    

    View Slide

41. Wrong choice
    

    View Slide

42. Incompetent leader.
    Seems good, but…
    Knows how to pretend.
    Affects everyone around.
    At best, is being ignored.
    

    View Slide

43. 4. The second approach.
    

    View Slide

44. To some extent, I meant it.
    Even more questions than
    before?
    

    View Slide

45. Hire or designate?
    

    View Slide

46. Seems more natural.
    It may be unfair, though.
    Sometimes it just can’t be fair.
    Designate?
    

    View Slide

47. A new star is born.
    A sheriff?
    Expectations.
    Hire?
    

    View Slide

48. Fresh air.
    Not a head start.
    A challenge.
    Hire?
    

    View Slide

49. http://leanpub.com/memoirs-of-a-software-team-leader/c/DoYouNeed
    30% discount for my eBook:
    

    View Slide

50. @lukaszwrobel
    Thank you!
    

    View Slide