Herding Tigers - Software Development and the Art of War
summary
Claims a small, cross‑functional “tiger team” (ideal size four devs + QA, product, occasional DBA/ops) yields huge gains: finished a 5‑week project in 7 days and the next in three days. Practices are concrete: QA and test automation from day one, continuous pairing/swarming, no meetings, war‑room seating, shared ownership, explicit leader intent, reward failure, and manager who protects the team. Result is faster cycles, faster recovery from bugs, and steadily improving process and velocity.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:47WARNING
- 1:50HERDING CATS!
- 2:13A ROCK BAND
- 4:08SOFTWARE DEVELOPMENT IS HARD!
- 5:02WHAT IS A TIGER TEAM?
- 5:19WHAT CAN YOU EXPECT FROM A TIGER TEAM?
- 8:10WHAT IS DIFFERENT ABOUT TIGERS?
- 8:56WHAT IS DIFFERENT?
- 10:08WHO IS ON A TIGER TEAM?
- 11:42WHY WARFARE?
- 15:54SPEED!
- 19:08COWS AND TIGERS 2
- 20:14LEADERSHIP
- 26:15NOTES ON AGILE ITSELF
related talks
01h 10mAgile Cross Team Collaboration How Tos
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
34mNative Agile Psychology of Teams and Individuals
48mBattlefield Agility: Think Beyond Scrum
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
59mDo You Know Da Wae
21mRadical Therapy for Software Teams
48mSoftware Teaming: Onboarding, Remote Work, Productivity — Four Years in an Team's Life