Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Geek's Guide to Leading Teams (Frontend Conference in Zurich, August 2018) frontendconference

432 visualizaciones

Publicado el

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 developers 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.

Publicado en: Software
  • Sé el primero en comentar

Geek's Guide to Leading Teams (Frontend Conference in Zurich, August 2018) frontendconference

  1. 1. Geek’s Guide to Leading Teams @patkua FrontEnd Conference (Zurich - July 2018) { }
  2. 2. » N26 is banking disruption writ large «
  3. 3. » N26 is the modern bank with 100+ deploys/week « enabled by a platform built with CD and Infra-as-Code
  4. 4. thekua.io/evolarch thekua.io/twtl thekua.io/retrobook CTO of N26
  5. 5. #leader #coach #architect #developer #life-long-learner #author We’re hiring in Berlin & NYC! https://n26.com/jobs/ CTO of N26
  6. 6. WHY do we need a Tech Lead?
  7. 7. ?
  8. 8. 11 http://www.flickr.com/photos/dcarlbom/3468358859/
  9. 9. What happens without Technical Leadership? All on the same project… 5 persistence frameworks 3 automated test frameworks 5 parallel branches A hand-rolled source control system
  10. 10. Think this doesn’t happen in the real world?
  11. 11. @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 @julianboot
  12. 12. TESTA simple for an effective Tech Lead
  13. 13. Does the codebase look like it was written by a single person? Yes No
  14. 14. WHAT does a good Tech Lead 
 focus on?
  15. 15. Programming People Process
  16. 16. Programming People Process
  17. 17. Programming
  18. 18. Programming Do effective Tech Leads need to code?DEFINITELY At least 30%of the time with the team
  19. 19. Programming
  20. 20. Programming “…respect is the currency of the realm”
  21. 21. Programming “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...”
  22. 22. Programming The Technical or 
 Post-Technical Divide AKA
  23. 23. Programming Consistency over Cleverness
  24. 24. Programming Consistency over Cleverness Tabs OR Spaces 2 OR 4
 spaces CamelCase OR Underscore Brackets OR Not
  25. 25. Programming Team Culture
  26. 26. Programming 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?
  27. 27. Programming What is your Technical Vision?
  28. 28. Programming People Process
  29. 29. People
  30. 30. People Strength in Diversity
  31. 31. People Strength in Diversity Intellection Woo Achiever Strategic
  32. 32. People or 100% +41% revenue Source: Diversity, Social Goods Provision, and Performance in the Firm (2014) MIT Research (2014)
  33. 33. People Source: The Mix That Matters: Innovation Through Diversity (2017) BCG Research (2017) Gender Age Country of
 Origin Academic Background Industry Career
 Path Positive correlation with innovation revenue
  34. 34. People Source: The Mix That Matters: Innovation Through Diversity (2017) BCG Research (2017) Gender Age Country of
 Origin Academic Background Industry Career
 Path Positive correlation with innovation revenue
  35. 35. People Collective Accuracy = Average Accuracy + Diversity* * Requires ability to integrate
  36. 36. People Growing People
  37. 37. People Growing People
  38. 38. People Growing People Skill/AbilityLOW HIGH ChallengeHIGHLOW Source: Csikszentmihalyi, Flow (1990)
  39. 39. People Growing People Skill/AbilityLOW HIGH ChallengeHIGHLOW Source: Csikszentmihalyi, Flow (1990) Anxiety
  40. 40. People Growing People Skill/AbilityLOW HIGH ChallengeHIGHLOW Source: Csikszentmihalyi, Flow (1990) Bored
  41. 41. People Growing People Skill/AbilityLOW HIGH ChallengeHIGHLOW Source: Csikszentmihalyi, Flow (1990)
  42. 42. People Learning Activities
  43. 43. People Brown Bag sessions Spike Showcases Team code reviews Technical Retrospectives Pair Programming Video/
 Book Club
  44. 44. People Source: “Bad Is Stronger Than Good” (2001) Baumeister et al
  45. 45. People Source: “Bad Is Stronger Than Good” (2001) Baumeister et al Beware the bad apple
  46. 46. Programming People Process
  47. 47. Process Is it okay to tell people what to do? Yes, but only sometimes
  48. 48. Process Tell Delegateor
  49. 49. Process Situational Leadership Model Tell DelegateSell Participate
  50. 50. Process Situational Leadership Model Skill Motivation Urgency
  51. 51. Process Tuckman’s Model
  52. 52. Process Tuckman’s Model Forming Storming Norming Performing Adjourning
  53. 53. Process “Essentially, all models are wrong, but some are useful.” —George E. P. Box
  54. 54. Process Make time for you
  55. 55. 59 http://www.flickr.com/photos/mbeo52/5062096969/sizes/l/
  56. 56. 60 https://www.flickr.com/photos/sushicam/5584789234/sizes/o/
  57. 57. Process Monday Tuesday Wednesday Thursday Friday 9AM 6PM Email Time Planning Time Email Time 1:1s Email Time Planning Time Next week planning Email Time
  58. 58. Programming People Process
  59. 59. One takeaway
  60. 60. Maker to Multiplier One takeaway
  61. 61. @patkua We’re hiring in
 Berlin & NYC! https://n26.com/jobs/ 
 Thank you { }

×