Technical agility - What, why and how?
summary
Argues technical agility means the code and platform let teams change product direction fast, with concrete practices: clean code and regular refactoring to lower cognitive load; cross‑functional teams that eliminate external handoffs; automated unit/integration/acceptance tests and reproducible dev environments; DevOps-style ownership to cut mean time to recovery (cites Netflix’s chaos monkey as a test of resilience); experiments and mob programming for faster feedback; measure lead time, cycle time and throughput, not lines of code.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:33Why agile?
- 3:48Different parts of agility
- 5:07Technical agility
- 6:39Clean code
- 8:18Low level of dependencies
- 12:09High level of automation
- 13:02Operational excellence
- 14:55Fast way for the team to learn together
- 17:41Measure the right things
- 19:32Summery
- 20:52Emergent architecture
related talks
44mWhat is true agile?
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
01h 31mAgility ≠ Speed - Agile Development
46mAgility and Architecture Together – Enabling a Fast Flow of Change
34mNative Agile Psychology of Teams and Individuals
35mAgility ≠ Speed
51mAgility at Scale: A Meeting of Mindsets
33mTransformation and agility: Key enablers of competitive advantage