Agile Software Testing
summary
Teams must shift testers from a late-stage checkbox role to proactive contributors who push testing into story breakdowns, pair with devs, and read code; adopt a whole team approach and favor T-shaped or generalized specialist skill mixes rather than forcing testers to write production code; build incremental automated regression checks starting with the newest stories so CI acts like a smoke detector (daily checks, not a replacement for human exploratory testing); ask "why" when testing piles up at sprint end and fix story sizing or testability.
AI-written summary · about
chapters (27)
- 0:00Intro
- 0:50Agile isnt brand new anymore
- 1:30What can testers do
- 3:37Common struggle for testers
- 4:50Twoway street
- 5:11Building credibility
- 6:46Tester vs programmer
- 7:03The testing mindset
- 8:10What happens if we do this
- 9:15The role of a tester
- 9:28Testers role
- 10:18Crossfunctional vs specialized areas
- 10:39Do Testers need to code
- 13:27Testing is a skill
- 15:06Task switching
- 15:34Is testing boring
- 16:06Idle time
- 18:20Common understanding
- 19:05Power of 3
- 20:34The whole team approach
- 21:11The time box
- 25:00Automation
- 26:07Automation run green
- 27:34Pilots and autopilot
- 28:33Haste
- 30:09Who is a tester
- 31:58Testing is boring
related talks
34mHelping Testers Add Value to Agile Projects
43mHow I fell in love with Agile testing and why you should, too!
01h 05mAdding value in an agile context
08mTesting In Agile
43mAgile Testing Practices for Better Software Quality
58mAppendix A: What We´ve Learned Since Agile Testing
36mWhole team quality: In the same boat or up the creek?
01h 02mAgile Testers and Test Managers: Now What?