Agile Development at Scale With Autonomous teams
summary
Claims that an API‑centric, domain‑aligned architecture lets teams own services and move fast, backed by a City of Oslo case with 300 components and several million lines of code as the outcome of moving from monolith to microservices; governance used: internal open‑source code, API management with tokens, centralized auth, weekly architecture council and tech leads as custodians; staffing rule of thumb is one ops per four developers plus tech lead and UX roles, and job‑satisfaction metrics guide restructuring and autonomy.
AI-written summary · about
chapters (10)
- 0:00Introduction and goals
- 2:08Defining success metrics
- 6:15The role of architecture
- 11:04Conway's law and autonomy
- 14:22Case study: City of Oslo
- 26:12Governance and standards
- 28:56Architectural governance
- 35:25Building balanced teams
- 40:16Knowledge sharing and culture
- 46:03Prioritizing job satisfaction
related talks
21mAutonomous Teams
48mTwo Dimensions Of Agile At Scale
39mAgility at Scale: A Meeting of Mindsets
15mThe agile leadership mindset: Embracing continuous change as a leader
38mMicroservices Architecture’s Influence on Team Organization
51mTech-enabled Network of Teams
31mThe Art of Scaling Agile & DevOps
16mEveryone architect!