17 / 55 · 23 QA Leadership & Mentoring · QA Culture and Advocacy← prev⊞ allnext →☰ Read as one page
2.9Turning Around a Toxic QA-Dev Relationship
When QA and development have an adversarial relationship, it poisons everything: bug reports become accusations, code reviews become battlefields, and sprint planning becomes a negotiation over testing time.
Root Causes of Toxic Relationships
| Symptom | Likely Root Cause |
|---|---|
| Developers dismiss bugs without investigation | Bug reports are poorly written or overly frequent on trivial issues |
| QA feels disrespected | QA is excluded from decisions and treated as a service function |
| "Works on my machine" wars | No shared definition of test environments and configurations |
| Bug ping-pong (open, close, reopen, repeat) | Unclear acceptance criteria and no shared understanding of "done" |
| Blame after production incidents | No blameless post-mortem process |
The Repair Playbook
- Acknowledge the problem openly. In a retrospective or team meeting, name the elephant in the room. "Our QA-dev collaboration is not working well. Let us figure out why and fix it."
- Pair up. Assign developer-QA pairs for one sprint. They sit together (or pair virtually), test together, debug together. Relationship problems dissolve when people work side by side.
- Establish shared standards. Co-create the Definition of Done, acceptance criteria format, and bug report template. When both sides own the standards, neither side feels imposed upon.
- Fix the bug report problem. If developers dismiss bug reports, the reports probably need improvement. If QA files too many low-priority bugs, agree on severity thresholds.
- Celebrate joint wins. When a sprint ships with zero escaped defects, celebrate the whole team -- not just QA for catching bugs or dev for writing clean code.