Downloaded 26 times
Uploaded bySylvain Wallez
Elastic - From 50 to 270, how to scale a distributed engineering team
The document details a presentation by Sylvain Wallez at DevFest Toulouse 2017, focusing on scaling a distributed engineering team at Elastic, a company with 600 employees across 32 countries. Additionally, it highlights their communication strategies, meeting structures, and the importance of transparency, autonomy, and trust within their organization. Key takeaways stress the need for open processes and adaptability as the team grows.
Elastic - From 50 to 270, how to scale a distributed engineering team
- 1. ‹#› Sylvain Wallez -@bluxte DevFest Toulouse, 2017-09-28 From50to270:Scalingadistributed engineeringteam
- 2. Who'sthisguy? Software Engineer -Elastic Cloud Previously tech lead, CTO, architect, trainer... ...at OVH, Actoboard, Sigfox, Scoop.it, Joost, Anyware Member of the Apache Software Foundation since 2003
- 3.
- 4.
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19.
- 20. Email:Filtersincluded How we reacheda decision
- 21.
- 22.
- 23.
- 24.
- 25.
- 26.
- 27.
- 28.
- 29. 20 @mention someone directly on GHissue instead of discussing in Slack
- 30.
- 31.
- 32. 23 Join any room Technicaldiscussions in public Public communication will educate everyone Post a summary to email or GitHub
- 33.
- 34.
- 35.
- 36.
- 37. 25 25 50 Demo DayDevStandups Collapses 25 Meetings
- 38. 25 25 Table Group 50 70 DemoDayDev Standups Collapses 25 Meetings
- 39. 25 25 Table Group 50 70 DemoDayDev Standups Collapses Collapses 7025 Meetings
- 40. 25 25 Table Group BlackBelt Session 50 70 140 Demo DayDev Standups Collapses Collapses 7025 Meetings
- 41. 25 25 Table Group BlackBelt Session Cross Product/ Per Product Sync 50 70 140 200 Demo DayDev Standups Collapses Collapses 7025 Meetings
- 42.
- 43.
- 44.
- 45.
- 46.
- 47.
- 48. Engineeringall-hands:2timesayear Vision, long termplans Talks from CEO, VPs and investors 2 days team time 1 day cross product 1 day fun activities
- 49.
- 50.
- 51.
- 52.
- 53.
- 54.
- 55.
- 56.
- 57.
- 58.
- 59.
- 60.
- 61.
- 62.
- 63. ReleaseProcess:Timebased Merge when readyand scalable Otherwise catch the next train No pressure on devs for pushing features
- 64.
- 65. How’stheorgstructure Flat org Self organisingteams Highly available
- 66.
- 67.
- 68.
- 69.
- 70.
- 71.
- 72.
- 73.
- 74.
- 75.
- 76.
- 77. Hiring “how many golfballs fit in an airplane ?”
- 78. Hiring “how many golfballs fit in an airplane ?”
- 79. Hiring No puzzle questions Eachteam has different interview styles Technical and team fit for distributed environment
- 80.
- 81. 59 0 10 20 30 40 50 0-3 3-6 9-1212-15 15-18 18+ Averageexperience
- 82. OnBoarding:Mentoring Day 1 High touchmentoring Mentor != Manager
- 83. OnBoarding:X-School Week-long orientation inMountain View, CA Meet team leads, product team Big Picture: Understand business functions
- 84.
- 85.
- 86.
- 87. Keytakeaways Don’t build processesaround mistakes
- 88.
- 89. Inclosing… They say itwon’t work at 50, 100, 500..
- 90.
- 91. Moreresources Initially presented asOSCon, Austin: https://conferences.oreilly.com/oscon/oscon-tx/public/schedule/detail/56992 https://www.elastic.co/elasticon/conf/2016/sf/inside-elastic-engineering https://www.elastic.co/elasticon/conf/2017/sf/on-distributed-systems-and-distributed-teams https://zachholman.com/posts/how-github-works/ Fonts and slide design were inspired by Zach Holman: https://zachholman.com/posts/slide-design-for-developers/