Why a Growing Company Needs a Growing QA Team
summary
Gives concrete outcomes: grew QA from 3 to 13 people over three years, moved testers left into kickoffs and refinements, found hundreds of bugs early, and turned part‑time testing on big projects into full‑time quality leadership. Drops heavy UI automation where ROI is poor and uses exploratory testing, Pareto focus, and data analysis (retention/crash metrics) instead. Builds a handbook, a QA books library, weekly workshops and uses JIRA + CI for structured reports; clients notice better delivery and management adds headcount.
AI-written summary · about
chapters (38)
- 0:00Intro
- 0:54QA Team
- 3:25Life at the Company
- 4:45Feedback from Developers
- 5:11Feedback from Designers
- 5:36Feedback from Project Managers
- 6:04QA doesnt know where it fits
- 7:12People dont communicate well
- 7:42I started asking questions
- 8:49We had to adapt
- 9:37Worst case scenario
- 11:37Tshaped QA
- 12:14How to build a Tshaped QA team
- 12:49What is context
- 13:58Manual testing
- 14:48User experience
- 15:20QA should grow up
- 15:43Green checks
- 17:02Changing context
- 18:12Variety
- 18:31Building a better QA team
- 20:57Collaboration
- 21:39Lack of Collaboration
- 22:49Team Effort
- 23:49Working with Product Owners
- 26:20Working with Designers
- 27:46Working with Developers
- 28:46Scrum Master
- 29:20Remove Tester Fatigue
- 29:44Be the Central Eye
- 29:59Knowledge
- 30:18Knowledge Sharing
- 30:41Workshops
- 31:16Conclusion
- 32:22Summary
- 32:59Our Job
- 33:24Lessons Learned in Software Testing
- 34:34Key Arguments for Growing QA Team
related talks
51mHow I lost my QA job
08m"How to Start a QA Department"
53mIs having a QA a symptom of a dysfunctional team?
27mProfessional Growth of the QA Engineer in Start-Up
21mEstablishing Quality Assurance in Startup environment
45mSame Old Story: Foundation of the QA Department. Tips and Tricks
43mLean QA: Automation, Monitoring, Experiments
42mEnsuring the Quality of your Quality Assurance