Library › Book 23 › Turning Around Toxic QA-Dev Relationships
Turning Around Toxic QA-Dev Relationships
5.1🔒Diagnosing the DysfunctionWhen QA and development have an adversarial relationship, it poisons everything: bug reports become accusations, code reviews become…
5.2🔒The Repair PlaybookIn a retrospective or team meeting, name the elephant in the room:
5.3🔒Dealing with Organizations That Do Not Value QA- QA is always the first budget cut - QA is not invited to planning or design discussions - "We do not have time for testing" is a frequent…
5.4🔒ExercisesBeginner: Identify one relationship friction point between QA and development in your organization. Which root cause from the diagnosis…
5.5🔒Q&AResume phrasing- Repaired a toxic QA-development relationship through a structured pairing program and co-created standards workshop, reducing bug…
5.6🔒Q&ACover letter framingWhen QA and development are adversarial, everyone loses: bug reports become accusations, planning becomes a negotiation over testing time…
5.7🔒Q&AInterview framing"I approach toxic QA-dev relationships by diagnosing the root cause, not just the symptoms. I use a structured repair playbook: acknowledge…
5.8🔒Q&AWhat not to say- "Developers do not respect QA" -- frames the problem as one-sided without examining QA's contribution to the dynamic. - "I enforce…
5.9🔒Q&AQuestion 1Prompt: You join a new team as a QA lead and discover that developers routinely close bug reports with "cannot reproduce" without any…
5.10🔒Q&AQuestion 2Prompt: Your QA team is not invited to sprint planning. The scrum master says "planning is for the delivery team." How do you get QA into…
5.11🔒Q&AQuestion 3Prompt: An engineering manager says to you: "We do not need a dedicated QA team. Developers should test their own code." How do you…