Stop 04 · SDLC, Agile & Testing MethodologiesTopics · 2/9

The QA Role in Scrum

In short

Scrum has no job called 'tester'. Everyone is a 'developer' in the team. So where does QA fit? Right in the middle of every conversation, from planning to demo.

QA engineers on a Scrum team typically test within the same sprint features are developed in, participate in ceremonies, and help define acceptance criteria — embedded in the team, not a separate downstream gate.

The purple blob checks a packed food box at a kitchen counter while a delivery rider waits with a helmet.

Think of it like this

The cloud kitchen packing station

In a cloud kitchen, the person at the packing counter checks every order before the rider leaves. But a good one also tells the cooks early, 'the biryani keeps coming back cold', so it's fixed upstream. That's QA in Scrum.

Watch it happen

QA through one Scrum sprint

Product owner

Developer

Story: saved cards

1/5In refinement, the product owner explains the story to the team.

The big ideas

What you need to know

Part of the team

QA attends standup, planning, refinement, review and retro like everyone else.

Shapes acceptance criteria

QA helps write clear pass/fail conditions for each story before work starts.

Quality is shared

Developers write unit tests and can test too. QA guides the approach, not just runs tests.

Retro is your stage

Retros are where QA can raise process issues, like stories arriving untestable on the last day.

Save yourself the pain

Common mistakes

Oops

Skipping refinement meetings because 'nothing is built yet'.

Do this instead

Refinement is where you prevent the most bugs. Always attend and ask questions.

Oops

Acting as a gate who only says pass or fail at the end.

Do this instead

Work alongside developers throughout the sprint and share test ideas early.

Your mission

Write acceptance criteria

~20 min

Quick check

In which Scrum event does QA have the best chance to prevent bugs before code is written?

Go deeper

1Read how QA responsibilities typically show up across Scrum ceremonies (planning, standup, review).
2Learn why testing within the sprint (not after it) is a core Agile testing principle.
3Understand this embedded model requires close, constant collaboration with developers.