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

It means testing 12+ stories plus regressions solo in two weeks — expect bottlenecks, blame, Friday crunches.

How to avoid QA becoming the scrum blocker?

Mandate pre-sprint test checklists, balance team ratios to 1:4, track escape rates over velocity.

Rarely past sprint 3; scale hires or embed testers, or watch bugs and burnout explode.

Agile promises shared quality. Reality for solo QA? You're the Friday savior — and the sprint villain. Here's the unfiltered truth from the trenches.

theAIcatchup Apr 10, 2026 4 min read

Solo QA in scrum turns you into the villain fast; math of throughput wins every time. 𝕏
Force test checklists in planning — it's the real shift-left, not slogans. 𝕏
Unbalanced teams risk Ariane-level failures; predict AI won't fully fix it soon. 𝕏

Published by

Ship faster. Build smarter.

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

Get the best Developer Tools stories of the week in your inbox — no noise, no spam.

Originally reported by dev.to