Quality Leadership: Building and Growing Strong Testing Teams
summary
Claims that the Belbin model produced the highest‑performing hires, that reducing QE headcount raised team efficiency, and that requiring basic API skills via Postman prevents dangerous skill gaps. Concrete practices include drafting seniority and salary standards, using assemble programming to justify one office day, and keeping teams through COVID by publicly making engineers the heroes. Notes focus on measurable outcomes, hiring tools, role definitions, and what actually changed.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:17Defining quality teams
- 11:23New QA lead collaboration
- 18:33Boosting team morale
- 26:03Fair workload distribution
- 32:03Office work policies
- 35:21Growing inherited teams
- 40:39Quality leadership strategies
- 41:41Testing leads reflections
related talks
17mStaying Ahead: The Future of QA Leadership
09m"The Tester’s Role: Balancing Technical Acumen and User Advocacy"
45mSame Old Story: Foundation of the QA Department. Tips and Tricks
36mWhy a Growing Company Needs a Growing QA Team
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
46mProject Culture and Team Responsibility for Quality
31mAssembling Excellence: Crafting a Quality Assurance Team from the Ground Up
51mQuality Assurance vs. Testing