Tech-enabled Network of Teams
summary
Argues that preserving team autonomy while scaling requires modular product design plus collaboration tech rather than more meetings and hierarchies. Gives concrete evidence: Linux grows to 55,000 contributors and solves two scaling crises by introducing modules and git; Amazon builds a “big red button” and an API mandate to eliminate cross-team chatter; a government loan platform ships in five days, handles €1bn in 28 hours and scales back to ~4 deploys/day after adding modular services, feature toggles and automated CI.
AI-written summary · about
chapters (9)
- 0:00Introduction to tech-enabled teams
- 3:34Journey to scaling agile principles
- 15:46Why Linux inspired team networks
- 22:51Network of empowered teams explained
- 28:59Building tech-enabled team networks
- 35:46Modular architecture and APIs
- 38:18COVID-19 loan platform case study
- 44:21Summary and takeaways
- 44:44Q&A session
related talks
21mAutonomous Teams
28mMaking do: Scaling expertise on teams you can't grow
47mMicroservices and the Inverse Conway Manoeuvre
46mLeading with Radical Transparency: Empowering Product Teams
39mTeam Topologies, Software Architecture & Complexity
58mScaling like a Silicon Valley startup
48mHow microteams change the way we collaborate. Again.
53mKeynote - Software Architecture, Team Topologies and Complexity Science