Sticking the Landing
summary
Maps technical debt to opportunity cost in story points and measures it: 2,600 total story points per year with 1,600 story points delivered as features and roughly 1,000 points lost to drag. Teams get a fixed budget each sprint to reduce debt, estimate features twice (actual vs ideal clean-config) to quantify the gap, and track the missed-delivery cost. The method uses story-point arithmetic, reuse of charts, and per-sprint remediation budgets; it produces actionable tradeoffs and measurable business-visible costs.
AI-written summary · about
chapters (11)
- 0:00Introduction and setup
- 1:30Planning the flight
- 4:18Emergency diversion
- 7:26Product owner requests
- 9:13Charlie’s speed lesson
- 10:40Approach and landing chaos
- 12:03Sticking the landing
- 13:32Measuring tech debt
- 15:43Budgeting for tech debt
- 17:08Communicating to business
- 18:36Call to kindness
related talks
06mManage your tech debt like a mortgage
39mThe cash value of technical debt - How to scare your boss into doing the right thing
15mEstimation and Trust-Driven Development
10mPaying down management debt without burning out
50mHow to defeat feature gluttony?
49mA Teacher, an Economist & a Developer Walk Into a Bar...
40mStory Points considered Harmful- a psychologist's thoughts on estimation
39mSoftware Craftsmanship