Tear Down the QA Wall
summary
Team gathers to answer three concrete questions—what do we do, how will we succeed, and what is most important right now—then chooses one immediate focus (example: definition of defect) and makes it a collective, repeatable commitment. QA joins planning and cross‑functional meetings, developers verify acceptance criteria before handoff, automation proofs‑of‑concept are shared (tools considered, pros/cons, learnings), and success is measured by clearer processes, fewer thrown builds and a goal to reduce bug introduction. Continuous repetition and leader backing reinforce the change.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:30Problems with throwing code over the wall
- 5:59Benefits of tearing down the wall
- 9:12Overcoming resistance to change
- 10:17Three key questions to build a healthy team
- 14:56Sustaining change and avoiding complacency
- 15:38Changing minds for healthy teams
related talks
53mIs having a QA a symptom of a dysfunctional team?
21mEstablishing Quality Assurance in Startup environment
45mSame Old Story: Foundation of the QA Department. Tips and Tricks
45mPractical Ideas on Building Quality Culture
45mWhat Would You Say You Do Here? Reframing Your Role In The QA Field
36mWhy a Growing Company Needs a Growing QA Team
37mDavy Kenis: QA No More: Revolutionizing Software testing
08m"How to Start a QA Department"