Chaos Development: Removing Software as the Inhibitor of Agile
summary
Argues that changing requirements demand two concrete practices: for stable domains, tiny classes, rigorous encapsulation and pair programming that produce models with ~2.3-line methods, 1,400 classes from a 72-class legacy and delivered a pension-replacement in 8 months for $1.1M achieving 6x productivity; for fuzzy domains, tiny asynchronous microservices on an event bus + microservices architecture (Kafka/RabbitMQ, Docker, Java) that ran 3,000 services under 100 lines and deploy every 3.5 minutes, generating rapid experiments and tens of millions in extra revenue.
AI-written summary · about
chapters (21)
- 0:00Start
- 13:03Requirements Uncertainty
- 13:49Agile at UK Retailer
- 14:31Guiding Light: XP Values
- 20:29Stories Assume Easy Change
- 21:57Replacement Application
- 25:24Implement Simple Design
- 26:58Craft The Model Carefully
- 28:4570's Design Approach
- 31:15Signs of Violation of Encapsulation
- 38:452. Delivery Focus
- 39:34Enhance Productivity
- 41:10Spreadsheet Fantasy!
- 45:43Handling in-Project Change
- 48:20Fuzzy Vision of "What" to Build
- 49:33Re-think Interactions
- 52:04Exploit Fuzzy Nature
- 53:27Summary Principles of MicroServices
- 54:48Count / Size Ratio
- 57:41Rapids, Rivers, and Ponds
- 58:19High-Performance Event Bus
related talks
45mYou can't be agile when you're fighting your code
38mConway's law in practice: Agile teams & Microservises
29mHow thinking small is changing software development big time
52mWithout Simplicity, There's Just No Agility
52mSmall Steps Are the Fastest Way Forward: Life Beyond Agile & Scrum
47mMicroservices and the Inverse Conway Manoeuvre
01h 01mArchitecting for rapid, frequent, reliable delivery of software.
01h 03mThe Magic of Small Things - 10 Years of Microservices