How to Succeed with Your Software Project
summary
Explains why projects fail with concrete failures: a $47M university system, $32M Hertz loss, $440M lost in 30 minutes and the Ariane 5 disaster, and cites Brooks’ rule that adding manpower to a late project makes it later. Advocates starting from customer value, building an MVP in nine days, short feedback loops (one–two week iterations), instrumenting systems and write code to test code, design for operations to avoid deployments that only support seven simultaneous users.
AI-written summary · about
chapters (6)
- 0:00Start
- 7:14Frequent, Direct, Feedback
- 8:47Write code to test code
- 9:44Embrace change
- 10:38Design for Operations
- 11:43Open all the Sources!
related talks
41mFailure is not an option. It's a fact
57mLearning from Failures
38mSimplicity: The Key to Software Success
07mFailure Is Not an Option It's a Fact
01h 00mThe Influential Software Engineer
41mHow to Turn a Failure into a Success
54mRuin Your Systems By Making Them Perfect
26mCommunication: What are you Thinking About?