Eliminate waste..are we doing it all wrong?
summary
Standish 2016 shows 30% of projects never complete and surviving projects overrun by ~190% while delivering 40–80% of scope, framing waste as a symptom not a cause. Examples: engineers never meet customers so teams build wrong products; 12 teams splitting a feature creates late integration bugs; product owners favor new features and force rework. Practical fixes include automated assistants that surface failing tests and create Slack subtasks, lock master when build fails defaults, and cultural shifts like praise effort and hunting bright spots to lower anxiety and cut waste.
AI-written summary · about
chapters (6)
- 0:00Introduction and future vision
- 7:03Waste in software development
- 12:57Waste as social defense
- 27:06Addressing anxiety in teams
- 35:25Reducing waste through positive change
- 37:35Q&A and closing
related talks
44m.tune - Eliminate Waste in SW Development
31mEngineering Effectiveness: Achieving your goals with less
40mHow to fail a software project fast and efficiently?
15mHow to NOT waste time
38mTools and methods are killing your products
30mAre You Doing Product Management or Bullshit Management?
46mFacilitation Foundations: Eliminating Waste From Agile Meetings
52mUnderstanding UnHealthy Syndromes of Software Delivery