Agility at scale
summary
A practitioner describes lessons from applying agile at large scale, focusing on how organizational design and enterprise IT architecture influence each other. The talk examines adapting agile team responsibilities to a non‑agile legacy system where business rules are dispersed across relational databases, transaction monitors, enterprise buses, applications and batch processes, and discusses how to redefine product teams around that technical landscape.
AI-written summary · about
chapters (11)
- 0:00Start
- 8:23We're not a startup Architecture
- 10:30We're not a startup Organization
- 12:29Agility requires... suitable tools
- 13:44Agility requires... decoupling
- 15:18Agility requires... understanding
- 16:13Agility requires... rigor
- 18:55Agility requires... taking a step back
- 20:28Agility requires... the involvement of the entire company
- 22:53Agility is yes, but be careful Don't cross the line either
- 23:47Agility is yes, but be careful It's not magic, it's demanding It's not doing more, faster, for less
related talks
26mAgile Transformations are not about software
43mResilience, Scalability, Performance – On the Architecture of Agile Product Teams
36mFrom Software to Systems: Modern Agility
35mAgility and Architecture - Do Opposites Attract?
48mTwo Dimensions Of Agile At Scale
01h 08mAgile Scalability — Comparing Models
40mHow to Be Large and Lean, Not Large and Fat?
38mAgile Architecture