Agile Engineering Fluency
summary
Argues that outcomes come from what teams are fluent at not what they merely aspire to, and provides a living engineering practices dependency graph on GitHub (JSON-backed, editable) that maps real prerequisites like automated developer tests → automated build verification → automated deploy. Presents measured claims: 9 different practices people call TDD, 14 senses of refactoring, pairing/mobbing reduce defects more than tests alone, typical teams take two to three years to gain fluency, and simple experiments (Kanban board → fewer status meetings) demonstrably work.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:40Dependency Chart
- 12:33Automated Deploy
- 16:10What Is the Definition of a Bug
- 18:11Definition of a Bug
- 23:46Hacks in the Code
- 24:50Plan Ahead Predictive Design
- 26:19Reflective Design
- 36:58When Do I Refactor
- 39:42Bdd and Tdd
related talks
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
55mAgile Engineering
36mWhat Your Mother Never Told You About Agile Development
46mAgile: principles over practices
57mEngineering for Software
46mIt’s XP Stupid!
34mNative Agile Psychology of Teams and Individuals
49mAgile is a Dirty Word