Why Promising Nothing Delivers More and Planing Always Fails
summary
Argues fixed-price fixed-scope projects misallocate risk and produce worse products and urges switching KPIs to startup-style measures: continuous delivery, zero cost of release, short feedback cycles. Recommends building small risk-neutral chunks (hours–a day), automated regression tests and fast containerized test runners under 250 ms, and measuring throughput of releasable increments. Cites a startup that went from six months stuck to two releases in a day after 1.5 weeks work and a bank rebuild that failed at ~1 billion kr with ~3 billion kr writeoffs.
AI-written summary · about
chapters (4)
related talks
45mBeyond Estimates
53m#NoProjects Beyond Projects - Why Projects Are Wrong & What To Do Instead
46mTalk about value, not testing – how to bring about rapid change
41mContinuous delivery in 10 easy mistakes
58mThe State of NoEstimates
28mUser Stories and other agile failures
45mThe Goldilocks Problem of Software Delivery
29mEconomies of Speed