It’s XP Stupid!
summary
Argues that teams claiming Agile but lacking XP practices produce legacy, fragile systems and unpredictable delivery, backing it with two project case studies where both a failing team and a “high-performing” team share no tests, tight coupling and “dragon” zones. Recommends concrete practices: pair/mob programming, test-driven development, trunk-based development, short spikes, tech-debt boards, automated deployments (Terraform + GoCD on AWS) and systematic assumption checks. Reports smoother onboarding, faster feedback loops and fewer handoffs when those practices are applied.
AI-written summary · about
chapters (10)
- 0:00Introduction and setup
- 2:20Why this talk matters
- 8:48Recap of Extreme Programming
- 13:55Twelve XP practices to adopt
- 33:16Managing technical debt
- 36:26Automated deployments and DevOps
- 38:54Testers as developers
- 41:01Tooling and feedback practices
- 43:28Onboarding and team resilience
- 44:52Summary and conclusion
related talks
36mWhat Your Mother Never Told You About Agile Development
23mMoving Fast with XP
26mXP in the 21st Century
38mPolyglot Agile
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
48mCreativity Before & After Agile
42mWhat your mother never told you about agile development
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell