Autonomous Teams
summary
Argues that microservices succeed only when six of nine recommended changes are about culture not tech, not just architecture, citing ThoughtWorks and AWS evidence that teams can scale faster than linear. Recommends products not projects, with managers making exactly four decisions (start product, add team, abandon product, disband team). Uses concrete practices: prototype demand like Dropbox’s fake explainer video, short implementation spikes removed from production, and bans on extra paperwork because a 15‑minute timesheet costs ~2 hours of decision capacity.
AI-written summary · about
chapters (11)
- 0:00Microservices to autonomous teams
- 3:36Synchronization to autonomy shift
- 5:19Products replace projects
- 7:25Four key decisions for product teams
- 9:12Prototyping over blind implementation
- 11:42Decentralized governance and guilds
- 12:47Reducing cognitive load
- 15:15Self-service in team decisions
- 16:42Finance, DevOps, security in teams
- 17:23Microservices vs micromanagement
- 18:29Q&A
related talks
47mMicroservices and the Inverse Conway Manoeuvre
51mTech-enabled Network of Teams
01h 01mRip It Up And Start Again?
01h 02mDesigning Microservices
47mEmbracing Microservices
44mIs It Time Already? Microservices Are Dead; Long Live Microservices!
39mThe Human Side of Microservices
57mEmbracing Microservices