Managing engineering teams through constant change
Constant changecaused by high attrition, frequent reorganization, shifting priorities, and management turnover, among other reasonsis the new normal. It takes months to onboard a new team member and get them adding value. Kathleen Vignos offers tips, shortcuts, and stories for stabilizing a team and finding a path to productivity amid the chaos.
| Talk Title | Managing engineering teams through constant change |
| Speakers | K Vignos (Twitter) |
| Conference | O’Reilly Velocity Conference |
| Conf Tag | Build Resilient Distributed Systems |
| Location | San Jose, California |
| Date | June 20-22, 2017 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
Constant change is all but inevitable on most software engineering teams. According to the Bureau of Labor Statistics, the median tenure for computer and mathematical occupations is just 4.4 years; software engineering teams often see developers rotate out after 2 years or less. Startups rise and fall. Reorganization is common. Attrition is high. How can you keep a team performing when the environment is in constant flux? Kathleen Vignos offers tips, shortcuts, and stories for stabilizing a team and finding a path to productivity amid the chaos as she walks you through engineering-specific real-world examples of how to keep #ShippingIt. Topics include:
![Queueing Theory, In Practice: Performance Modelling in Cloud-Native Territory [I]](/2017/images/all/lf_huffc03acb4b89c823f315cae16e4b2e6b_29065_700x350_resize_q75_box.jpg)
