Building a high quality product
summary
Advocates shipping every commit to production, rolling forward with fixes, and using CI/CD, feature toggles and monitoring to decouple deployment risk from release risk; replaces fragile end-to-end tests with a testing pyramid plus consumer-driven contracts for microservices; enforces work-in-progress limits to drop cycle time from ~15 days to ~1 day and raise velocity; cites teams reaching thousands of deploys per week with fewer customer-facing errors; uses pairing, timeboxed spikes, and cross-functional collaboration to bake quality in.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:25About No Thought Works
- 1:14What is quality
- 2:41What do we do
- 5:25The process
- 12:32Test automation
- 15:16Feature toggle
- 17:04Monitoring
- 18:05Auto Auto
- 20:26Business Analysts
- 21:04Quality
- 22:59Edge cases
- 23:58Business advantage
- 25:23Working with team
- 25:43Avoid sunk cost fallacy
- 26:37Outcome bias
- 27:30Overconfidence
- 28:24Availability bias
- 28:54Social proof bias
- 30:03Mistakes
- 33:39Diversity and inclusiveness
- 35:30Have fun
related talks
35mBetter, Faster, Stronger - Delivering High Quality Products
33mSoftware development practices for companies that want to make an impact
28mHow to ship apps better, faster, stronger
34mEnabling a Continuous Deployment Mindset
44mRelease Early, Often, Stable
40mContinuous Delivery Anti-Patterns
40mAvoiding release paralysis
33m7 habits of a high performing team