What are the two responsibilities of testers in a Scrum Team? (choose the best two answers)

Question

Options

• ATracking quality metrics.
• BScrum has no "tester" role.
• CVerifying the work of programmers.
• DThe Developers are responsible for quality.
• EFinding bugs.

Explanation

In Scrum, there is no defined "tester" role - the Scrum Guide does not recognize it as a named position. This makes B correct: Scrum simply has no "tester" role. The follow-on is D: quality is the collective responsibility of the Developers (the cross-functional group that builds the product), not a siloed individual. Options A, C, and E are wrong because they all assume a dedicated tester exists and performs specialized duties (tracking metrics, gatekeeping programmer work, hunting bugs) - exactly the kind of siloed, handoff-based thinking Scrum is designed to eliminate. Options C and E are particularly tempting but describe a traditional QA role, not a Scrum role.

Memory tip: Think of it as a two-part mantra - "There is no tester" (B) + "Developers own quality" (D). Any answer that assigns testing duties to a named individual contradicts Scrum's cross-functional, whole-team ownership model.

No community discussion yet for this question.