Stickies on the wall will not help you if...
summary
Claim: corporate Agile rituals fail if code quality and technical practices are missing. Evidence: teams using Scrum or Kanban still stall because they keep project thinking, accumulate technical debt, and can’t change code cheaply. Concrete practices promoted: automated tests as assurance of changeability, decompose products into small independent subproducts (Spotify example) and hire learners not heroes. Surprising number: many orgs report near zero success on big projects unless product decomposition and engineering discipline exist.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:56Customer collaboration
- 3:42Agile misconceptions
- 7:41Change as constant
- 9:52Project thinking vs agile
- 12:21Product quality focus
- 13:46Software craftsmanship
- 15:56Hiring passionate learners
- 17:44Blameless culture
- 18:45Scaling agile failures
- 21:39Elephant carpaccio approach
- 23:24Agile business reason
- 25:27Summary