A puppy dies when agile meets reality
summary
Weekly comic strips expose concrete anti‑patterns: keep 70% capacity not 100% commitment, never compare team velocities, treat knowledge sharing as an investment not lost velocity, and categorize teams via Team Topologies but fix root causes by remove dependencies rather than buying SAFe. Architecture uses automated fitness functions (performance, security, complexity) to prioritize NFRs. Claims include 74,000 LinkedIn followers, workshops and books sold, and a live rap/guest bit — humor aims to surface failures so organizations can actually change, not just rebrand.
AI-written summary · about
chapters (18)
- 0:00Intro
- 1:00About Luxshan
- 3:02Agile is not working
- 4:40How to become an agile coach
- 6:22What we want to teach managers
- 11:03How do we fix it
- 11:59Consultants have an answer
- 14:45The big boss
- 16:26The PO role
- 19:10Scrum Master
- 21:33Focus
- 23:37Psychological safety
- 27:08Emotional intelligence
- 30:37Teams have dependencies
- 33:42The architect
- 38:14Scaling agile
- 41:29Communication
- 42:24Surprise
related talks
44mHow comic strips connect agile and architecture
42mComic Strips: Learn From Others' Agile Failures
53mAgile and Architecture: a meeting of the undead
47mAgile and Architecture: a meeting of the undead
37mSoftware Architecture for Humans!
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
48mDown the Ivory Tower towards Agile Architecture
13mAgile Architecture: Enabling Innovation in a Rapidly Changing World