Team Topologies, Software Architecture & Complexity

on YouTube ↗39m

" summary

Argues that team structure drives architecture and scaling using Team Topologies’ four team types, value‑stream maps and Santa Fe Institute scaling laws; shows Amazon’s forcing functions (interface contracts, team size limits, externalizable services) produce a 1.15 exponent — doubling people yields >double revenue — while typical firms follow ~0.85 scaling. Uses DORA’s four metrics and empirical company/city data to diagnose aging (corporate metabolism) and warns change request boards predict low performance as a concrete, measurable failure mode.

AI-written summary · about

" chapters (11)

1. 0:00Intro
2. 3:42Team Topologies & complexity
3. 5:52What is value?
4. 8:04Team Topologies
5. 10:25Software architecture & complexity
6. 14:17Complex adaptive systems
7. 23:05Complex adaptive systems are everywhere
8. 24:15Corporate metabolism
9. 28:54Sidebar: Identifying the signs of ageing
10. 32:54Scaling complex adaptive systems
11. 37:39Outro

" related talks

• 49mSoftware Architecture, Team Topologies & Complexity ScienceJames Lewis · YOW! Melbourne 2022
• 01h 01mSoftware Architecture, Team Topologies & Complexity ScienceJames Lewis · YOW! 2021
• 53mKeynote - Software Architecture, Team Topologies and Complexity ScienceJames Lewis · NDC Porto 2022
• 48mScale, Microservices and FlowJames Lewis · Build Stuff 2019
• 37mScale, Flow and MicroservicesJames Lewis · GOTOpia February 2021
• 42mScale, Flow and MicroservicesJames Lewis · GOTOpia Chicago 2021
• 45mTowards Architecture Organization Topologies for Sustainable Fast Flow of ChangeEduardo Da Silva · Agile meets Architecture Berlin 2023
• 44mFlow, microservices and scale｜James Lewis · Øredev 2019