62 / 66 · 20 Agile & Scrum · The QA Role Evolution← prev⊞ allnext →☰ Read as one page
9.6How to Transition from Gatekeeper to Coach
If you are currently in a gatekeeper role, here is how to transition:
Step 1: Start Contributing Upstream
- Ask to attend sprint planning. Bring specific, useful questions about testability.
- Offer to review PRs. Start with test code reviews, then expand to application code.
- Propose a three amigos session for the next complex story.
Step 2: Build Technical Credibility
- Learn the tech stack well enough to read and review application code.
- Write test automation that developers respect (clean, maintainable, well-structured).
- Improve the CI pipeline (faster, more reliable, better artifacts).
Step 3: Share Responsibility
- Help developers write their own tests. Coach, do not gatekeep.
- Create testing guidelines that the whole team follows.
- Make quality everyone's goal, not just QA's.
Step 4: Demonstrate Value Through Prevention
- Track how many bugs are caught in requirements review vs in testing.
- Show the cost savings of early bug detection.
- Report on escaped defects and what process changes would have caught them.