The Goldilocks Problem of Software Delivery
summary
Claim: move focus from builds or monolithic releases to features are the unit of value; evidence: microservices correlate with a 3x better likelihood of 15%+ revenue growth and DORA shows elite teams outperform by two to three orders of magnitude. Tools and tactics: reliable CI quality signals (no flaky tests), feature flags decouple deployment from release enabling gradual rollouts and quick rollback, agile tooling and dashboards that surface PR latency (avg ~4 days) and blockers, and value stream mapping exposes 90–95% wait time to prioritize unblocking the few things that move value.
AI-written summary · about
chapters (14)
- 0:00Intro
- 2:48CI/CD Practices & DevOps Drives Speed & Quality
- 6:34These Practices Are Helping, Yet Problems Still Exist
- 8:50Digital Transformations Must Extend Beyond Dev & Ops
- 9:49"Release" is the Enterprise Challenge
- 12:52What is the Goldilocks Problem of Software Delivery?
- 20:21relying on multitude of tools across large variety of functions within the business
- 24:18As tasks are processed by the people and tools, some get blocked while others move forward.
- 26:19We need to make sense of all the information and noise across teams and tools.
- 27:21We must surface the context needed to build the right features, excite users and win customers.
- 28:36Focus on Unblocking Features
- 29:57Some practical advice
- 35:27Agile Tooling is Your Friend
- 36:13Feature Flags are Your Friend
