Heavyweight agile methods?!? Let’s make them Lean(er).
summary
Argues that Lean provides concrete fixes for heavyweight Agile: explains pull as system property with WIP targets not personal choice, treats one-piece flow ≠ batch size one as reducing idle time and designing flow, and defines autonomation (jidoka) as automation that enables people not replaces them. Covers visual management, gemba walks, Improvement Kata, built‑in quality that stops the line, and practical changes like owning pipelines, surfacing metrics on login pages, and reframing Kanban and Scrum practices with explicit takt and flow.
AI-written summary · about
chapters (10)
- 0:00Introduction and history
- 4:29Customer driven vs rhythm
- 6:56Pull system explained
- 11:01One piece flow concept
- 16:04Autonomation and mastery
- 19:58Built-in quality in processes
- 23:09Visual management and Gemba
- 28:05Highest quality lowest cost
- 33:26Opportunities for improvement
- 39:07Q&A and conclusion
