Developer + Tester = Quality++
summary
Explains why pairing a developer and a tester improves product quality in Agile teams, naming the developer-tester pair as the focus. Describes concrete practices and approaches for collaboration at each stage from requirements to customer acceptance, and outlines practical advantages for both roles.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:47Devs and testers
- 8:20Role split history
- 11:27Modern team issues
- 13:32Planning goals
- 16:42Acceptance criteria
- 18:48Testing phase interaction
- 21:38Test scenarios
- 25:48Pair design sessions
- 29:38Early test automation
- 32:46Demo benefits
- 35:34Procrastination and Parkinson’s
- 37:40Code review pairs
- 41:11Pair testing
- 42:54Shared quality ownership
- 45:21Summary
related talks
49mDeveloper + tester = quality++
36mWhole team quality: In the same boat or up the creek?
21mImproving Quality Through Effective Communication Between Tester and Developer
08m“Three Paths to Better Developer Testing”
30mCollaboration Between the Dev and the Test Team
37mWe Are The Testers: You Will Be Assimilated
43mAgile Testing Practices for Better Software Quality
35mTesting != Quality