1 / 47

The Geek's Guide to Leading Teams

The most challenging aspects to software development are always the people issues. Picking the right data structures, finding the right testing approaches are simple compared to building an effective software team. Most organisations fail to support developer promoted into technical leadership roles so where do you go to uncover the secret skills behind this important role. Come along to this session to discover practical tips for leading technical teams.

thekua
Télécharger la présentation

The Geek's Guide to Leading Teams

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Geek’s Guide to Leading Teams Patrick Kua @patkua

  2. Available on leanpub (http://tiny.cc/twtl)

  3. Why do we need a Tech Lead?

  4. Why do we need a Tech Lead?

  5. ?

  6. @julianboot @thejayfields: I had ten guys on my last project, all of them had opinions and all of them were expressed in the code base #speakerconf Source: http://twitter.com/julianboot/status/232830267822309376

  7. A simple test for an effective Tech Lead...

  8. Does the codebase look like it was written by a single person? Yes No

  9. What do effective Tech Leads focus on?

  10. People Tech Business You

  11. The “Tech” in Tech Lead

  12. Do effective Technical Leaders need to code? Definitely! At least 30% of the time with the team TECH

  13. http://bit.ly/15Rm4z

  14. “...respect is the currency of the realm” http://bit.ly/15Rm4z

  15. ““The amount of respect an IT pro pays someone is a measure of how tolerable that person is when it comes to getting things done...”” http://bit.ly/15Rm4z

  16. Consistency over Cleverness

  17. http://www.emacswiki.org/emacs/TabsSpacesBoth

  18. Brackets OR not Curly brace end of line OR next line Tabs OR Spaces 2 Spaces OR 4 Spaces CamelCase OR Underscore

  19. Team Culture

  20. Team Culture How long does the build stay broken? Do people avoid conflict? Do people offer new ideas? Do people flag when they need help? Do people feel okay to admit being wrong?

  21. Vision

  22. Vision Can everyone draw the same architecture diagram? Yes No

  23. Free download: http://bit.ly/1Esrn7f

  24. Riding Paradox

  25. Riding Paradox Consistency vs Improvement Delivering vs Learning Technical vs Business “Paradox” by Michael Berg

  26. People

  27. Woo Intellection Strategic Analytical Achiever Activator Input

  28. Collective Accuracy Average Accuracy + Diversity* = * Requires ability to integrate

  29. Trust isn’t built in one day

  30. Growing People

  31. HIGH Challenge LOW Skill/Ability HIGH LOW

  32. HIGH Anxiety Challenge LOW Skill/Ability HIGH LOW

  33. HIGH Challenge Boredom LOW Skill/Ability HIGH LOW

  34. HIGH Flow Anxiety Challenge Boredom LOW Skill/Ability HIGH LOW

  35. Brown Bag sessions Team code reviews Pair Programming Learning Activities Spike Showcases Video/Book Club Technical Retrospectives

  36. Beware the bad apple “Bad Is Stronger Than Good” (2001) Baumeister et al

  37. Bridging the Business

  38. Translating between realms Technical Business

  39. Business Opportunities

  40. You

  41. Monday Tuesday Wednesday Thursday Friday Email Time Email Time 9am Email Time Email Time 1:1s Planning Time Next week planning 6pm Planning Time

  42. People The Tech of a Tech Lead Bridging the Business You

  43. Questions? Patrick Kua @patkua

More Related