SWARMing: Scaling Without A Religious Methodology
summary
Claim: packaged scaling methods inevitably degrade, dysfunction and expire, so scaling by stricter adherence fails. Uses throughput accounting ideas and measures like lead time and throughput, applies Theory of Constraints to find one bottleneck at a time, and uses concrete practices: value‑stream mapping, small cycles of visualize stabilize optimize, and three‑to‑five year investment plus leadership with access and influence. Results: measurable reduced lead times and clearer constraints, not instant fixes but steady improvement when teams commit time, practice, coaching and cross‑stakeholder communication.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 6:30Cost Accounting
- 16:30Why is it not working
- 19:05Characteristics of existence
- 24:50The inevitable
- 27:34Packaged solutions
- 29:31Religion
- 31:47Scaling without a religion
- 36:59Summary
- 38:39Conclusion
related talks
47m7 Sins of Scaling and Other Agile Anti Patterns
43mSoftware Engineering Management at Scale with the Theory of Constraints
51mMastering Trade-offs for Scaled Agile Success
48mScale, Microservices and Flow
49mSoftware Architecture, Team Topologies & Complexity Science
42mScale, Flow and Microservices
31mScaling
39mDesigning an Organization, Lessons from scaling technical orgs