How programmers & testers can be productive
summary
Teams implement CI/CD + unit tests and automation run on merge and report catching regressions early, pairing developers with QEs to fix blockers within hours. They schedule weekly defect triage and a final code-freeze week so testers get a full sprint to run manual and smoke suites, run cross-team bug bashes, and track customer feedback in a monthly loop. Resource planning targets a 3:1 developer:QE ratio and reward points for contributors, reducing post‑release bugs and speeding merges.
AI-written summary · about
chapters (17)
- 0:00Developer-tester collaboration
- 1:26Topic and agenda
- 3:10Waterfall to agile evolution
- 5:28Developer-tester conflicts causes
- 10:25Solving conflicts with teamwork
- 13:13Resource alignment strategies
- 15:22Pair programming benefits
- 16:04Shift-left testing
- 18:11CI/CD pipeline improvements
- 19:58Cross-functional bug bashes
- 21:24Feedback loop participation
- 23:12End-to-end deployment
- 25:18Continuous improvement tips
- 27:05Closing remarks
- 27:56Q&A: Code merge quality
- 30:24Q&A: Collaboration culture
- 32:54Q&A: Peer programming
related talks
36mHow to defuse a bomb Wait, I mean a bug
36mWhole team quality: In the same boat or up the creek?
25mProgramming to the extreme
01h 09mScaling up with Embedded Testing
31m#testedAF: Test All the Things (Not Just Your Units)
08m“Testers! Aim to Enable”
46mProject Culture and Team Responsibility for Quality
41mShift Left, Shift Right and Improve the Centre