You Can't Be Agile If Your Testing Practices Suck
summary
Claim: Agile fails when testing and engineering practices don’t prevent rot. Evidence: a delivered international web app for a Swiss bank, a corporate goal to make 50% of projects agile, and recurring slowdowns from messy code. Concrete remedies: measure value with release frequency, customer satisfaction and pirate metrics; use test-driven development, refactoring and strong-style pair/mob programming; enforce code reviews, GitHub pull requests and JIRA workflows; budget 20–40% time for quality and run root-cause analysis with automated checks so fixes actually stick.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:49What is your current pain? What
- 6:59Agile is not
- 16:23Major challenges
- 22:32Broken Window Theory
- 26:29Mob Programming
- 28:24Without Tests
- 32:53Proper Root Cause Anal
related talks
39mMyths & Challenges of Agile Testing
24mImproving Development Quality and Speed with Agile Testing
51mDon't Kill Agility with Agile Processes
40mRegain Benefits from Agile Software Development
38mPolyglot Agile
43mHow I fell in love with Agile testing and why you should, too!
43mAgile Testing Practices for Better Software Quality
42mWhat your mother never told you about agile development