What A QA Actually Does In A Scrum Sprint

Sprint planning — read every story. Add acceptance criteria the devs missed. Estimate test effort.

Days 1–3 — write test cases for the stories starting first. Pair with developers on edge cases.

Days 4–7 — test as features land. File bugs the moment you see them; don't batch.

Days 8–9 — regression pass on the rest of the product. Smoke automation runs nightly.

Day 10 — sign off, demo with the team, retro. Note what slowed testing down.