Agility, Craftsmanship and Cargo Cult: What's the Link?
summary
Presents data showing most delivered features go unused, large cloud and development waste, and heavy costs from technical debt. Calls out cargo-cult behaviors—superficial hexagonal architecture, TDD done without refactoring, conflicting DDD interpretations, and onerous merge approvals—and recommends diagnosing specific failures, aligning product and technical choices, measuring actual usage, and addressing root causes instead of copying labels.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:03Personal experience and culture
- 3:54Alarming feature stats
- 6:24Risks and best practices
- 8:14Agility and craftsmanship defined
- 9:57Agile and craft values
- 12:06Cargo cult explained
- 14:39Organizational cargo cult
- 16:06Technical cargo cult
- 17:53Tools without values
- 18:56Continuous improvement and pragmatism
- 21:24Conclusion and call to action
- 23:23Q&A
related talks
38mAgile, Craftsmanship, DevOps and other monsters [...]
44mDependencies; Devil or Darling?
46mIt’s XP Stupid!
44mCruft and Technical Debt: A Long View
49mExtreme Professionalism - Software Craftsmanship.
34mBuilding a Culture For Developer Productivity
26mSoftware Delivery from First Principles
52mUnderstanding UnHealthy Syndromes of Software Delivery