How to Build More Effective Relationships with Your Developers
summary
Says poor communication costs U.S. businesses $1.2 trillion a year (~$12,506 per employee) and offers concrete fixes: stop waiting to test, adopt test early test often, run weekly dojos and Test Automation University lessons, pair using Strong Style pairing and devbox testing, tag defects found in paired sessions and track cycle time, rejection rate and DORA metrics with context, experiment with a visible hypothesis/measurement loop, and use videos or internal belts to win management buy-in.
AI-written summary · about
chapters (14)
- 0:00Introduction and welcome
- 2:30Why relationships with developers matter
- 4:16Unlearning old testing mindsets
- 8:27Effective pairing strategies
- 12:22Measuring collaboration effectiveness
- 15:15Encouraging test-first approaches
- 22:40Modern Agile and shifting left
- 27:21Building trust with developers
- 33:25Connecting developers to customers
- 37:14Probing questions for risk areas
- 39:46Tying QA metrics to developer output
- 45:29Live audience Q&A session
- 58:39Supporting non-tech founders
- 1:01:06Rapid-fire wrap-up and closing
related talks
21mDevelopers vs Quality Assurance
01h 04mBuilding on Success, Beyond the Obvious
58mDeveloper Joy – How Great Teams Get S%*t Done
24mImproving Development Quality and Speed with Agile Testing
44mDeveloper Joy – How great teams get s%*t done
17mMake Work Not Suck Improving the Developer Experience
25mHow to Transform Dev and Test Silos into a Team
47mDevelopers Are (Not) Lazy! Why is It So Difficult to Get Programmers to Do Unit Testing