What does being the only QA in a scrum team really mean?

It's testing 12+ stories solo per sprint, amid 'quick checks' pleas, while burndown blames you.

How to fix QA bottlenecks in agile teams?

Mandate planning test cases, 1:3 QA-dev ratios, and exec demos of risks—not just blog posts.

Math says no; real teams say fight or flee before the prod outage hits.

Six developers, one QA. That's not a team; that's a bottleneck waiting to explode. Here's the unvarnished truth from the trenches.

theAIcatchup Apr 10, 2026 4 min read

Solo QA in 6-dev teams turns into 'the blocker' by sprint three—math doesn't lie. 𝕏
Enforce written test criteria in planning; it's the real 'shift left,' won through fights. 𝕏
History warns: this setup echoes waterfall fails, heading for burnout spikes. 𝕏

Published by

Community-driven. Code-first.

#QA bottlenecks #agile challenges #agile pitfalls #agile realities #agile testing pitfalls #scrum bottlenecks #scrum team #scrum teams #scrum testing #shift left reality #solo QA #solo QA scrum #testing bottlenecks

Get the best Open Source stories of the week in your inbox — no noise, no spam.

Originally reported by Dev.to