Scaling tech processes and team
summary
Describes challenges of growing engineering teams and technical processes at scale, and presents concrete practices for evolving organization, communication, delivery and ownership as teams expand. Names approaches like process standardisation, role clarification and scaling delivery pipelines to keep quality and velocity when moving from small to larger teams.
AI-written summary · about
chapters (24)
- 0:00Intro
- 0:12A few words about myself
- 2:23Highload
- 3:57Branching flow: Master only
- 4:23Branching flow: Gitflow
- 5:13Branching flow: Skullcandy
- 6:07Branching flow: trunk based dev
- 8:48CVCD evolution (3)
- 12:19Tests: Framework
- 13:36Tests requirements
- 15:22Infrastructure
- 15:33Docker: Onboarding example
- 16:59Terraform example
- 17:20Kubernetes
- 19:38Code reviews: pull reminders
- 23:11Feature toggles
- 25:05OPS: Monitoring
- 25:35OPS: Alarming
- 26:01OPS: Postmortems
- 27:15Processes: Security
- 30:31Scale the team: Hiring
- 33:52Maintain and develop culture
- 36:08Scale the team: Team structure
- 37:05Final thoughts
related talks
43mScalability of a Team / a Technical Division
31mScaling Tech Organizations
16mEnlarge your team!
19mScaling Fast – Engineering Lessons From ~15 Years of Tech Startups
53mThe art of scaling an Engineering Organization
26mScaling engineering organizations
48mHow to scale not only IT systems but also IT teams
32mScaling Systems and Teams Together