Polyglot Agile
summary
Argues that agility fails without a technical foundation: version control, automated test suites, continuous integration and delivery, monitoring and refactor time are required so teams can actually change the product. Describes an enterprise where one coach for 700 devs, 15‑minute trainings, stage/gate + Scrum and week‑long OKR workshops produce inertia, destroyed teams and inability to act on feedback. Recommends practices that work in the wild: commit to trunk, pair programming and blameless retrospectives, plus stepwise change, celebrate small wins and dedicated coaching.
AI-written summary · about
chapters (18)
- 0:00Intro
- 1:48Takeaway message
- 3:11The growth mindset
- 4:08Types of organizations
- 5:37Different processes
- 9:47Problems
- 17:10Fluency
- 21:44Happiness
- 24:07Technical foundation
- 25:37Legacy systems
- 26:16Stupid developers
- 26:58Technical Agile Fluency
- 27:25What do we need
- 30:11Editorial transformations
- 30:49Patterns for change
- 32:24Parents
- 34:14Test the waters
- 37:08Agile is a journey
