Balancing individual team flow with cross-team collaboration
summary
Building a robotic vacuum with roughly 20 teams across four countries exposes that splitting work via Team Topologies reduces local cognitive load but not end-to-end delivery speed because integration and testing still bottleneck releases. The team uses Team of Teams ideas: fortnightly cross-team demos, a daily rep sync, temporary cross-functional triage teams that find root causes far faster, and one-person rotations of about 10–20 week rotation to spread system knowledge. Sensor tuning on real homes repeatedly shows why interfaces and shared consciousness matter.
AI-written summary · about
related talks
35mHow a Lean and Structured Team Topology amplifies an Organisation's Productivity
01h 05mSoftware Teaming (Mob Programming) and the Power of Flow.
45mLessons learned from introducing Team Topologies
52mCross functional teams are great - but what about the business?
54mThe value of Org Topologies in the era of DIY-frameworks
37mDevOps Topologies 10 years on: what have we learned about silos, collaboration...
01h 10mAgile Cross Team Collaboration How Tos
01h 00mDynamic Teams - Fluidity for the win