Agility in Software Architecture
summary
Argues agility is an adjective not a process and proves it with concrete moves: Branson sells a 39‑seat charter on cardboard; a feature fake shown to 100 users yields only 6% interest so the feature is not built; HP accumulates 36 billion lines of firmware and then refactors into a future‑smart shared core; a 30‑person team delivers a single correct report line in a week using a walking skeleton; teams adopt record‑and‑playback tests, write a bespoke ORM in two days and start minimal and evolve.
AI-written summary · about
chapters (12)
- 0:00The agile traveler
- 1:47Redefining agility
- 4:37Feature faking techniques
- 8:10Six mantras of agility
- 10:48Wisdom of John Wooden
- 14:25Avoiding rigid systems
- 18:50Known vs unknown problems
- 23:01Leveraging existing tools
- 25:00Evolutionary design
- 28:01Vertical slicing for change
- 31:19Driving out fear
- 35:26Poise and balance
related talks
46mAgility and Architecture Together – Enabling a Fast Flow of Change
41mArchitecture and Agility: A Shared Skillset!
01h 07mAgility is the Tool, not the Purpose
38mAgile Architecture
13mAgile Architecture: Enabling Innovation in a Rapidly Changing World
38mPolyglot Agile
36mFrom Software to Systems: Modern Agility
01h 00mAgile Architecture