Value and waste in software engineering
summary
Presents a concrete definition of waste with nine categories of waste and empirical causes, catalogs specific review smells — “looks good to me,” review buddies, ping‑pong, sleeping, large change sets — and links each to the resulting rework or delay. Shows that technical‑debt types behave differently: code/defect debt is often self‑fixed while design debt requires planned, senior‑led remediation. Delivers operationalized human values (dignity, inclusiveness) mapped to concrete requirements.
AI-written summary · about
chapters (6)
- 0:00Intro
- 1:42What is waste?
- 2:50Waste - bad code reviews
- 5:28Waste - technical debt
- 7:21Value - human values?
- 9:56Summary: create value + reduce waste
related talks
45mSoftware's Seven Deadly Wastes
01h 05mWasteful Waste or Why Everything Is Usually So Slow in Development
55mMuda, Mura, Muri: myths and practices applying Lean Software Development
48mPut 5 Euros in the Software Engineering Phrase Piggy Bank
28mTechnical Debt: Why it'll ruin your software
57mPutting an end to "technical debt"
25mDemystifying Technical Debt
01h 06mKeynote - THE MISMEASURE OF SOFTWARE