Agile Cross Team Collaboration How Tos
summary
20 years of lessons claim two practical strategies and their tradeoffs: start with shared product code ownership — long‑standing feature teams, pairing and pay rotation, continuous integration, trunk‑based development and frequent releases — which worked at Ferrari until some modules stabilized and then moved to team-level code ownership. The concrete advice is to eliminate dependencies first (automate or expose services), prefer parallel or feature‑toggle sequencing, measure speedups, and expect limits like unlearnable skills or political silos.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:47Why collaboration matters
- 7:14Shared work strategy
- 15:09Feature teams and specialists
- 21:09Shared work limits
- 26:24Team topologies for dependencies
- 34:14Eliminating dependencies and Conway’s law
- 42:31Collaboration success factors
- 46:05Shared vs team code ownership
- 51:48Legal concerns in collaboration
- 53:35Accidental dependencies
- 56:04Agile and Scrum compatibility
- 1:01:44Experimentation periods
- 1:05:58Q&A
related talks
18mAgile leadership and technical mastery, a harmonious alliance
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
51mSabotaging a Transformation
26mThe Rise and Fall of Feature Teams
55mGetting Unstuck Strategies for Surviving in a Rapidly Changing Post-Agile World
49mHow to Make People Work Together?
26mAgile values and principles for non software teams
51mMastering Trade-offs for Scaled Agile Success