The Scrum Guide defines only three specific accountabilities within a Scrum Team: Product Owner, Scrum Master, and Developers. There is no distinct "Tester" role. Individuals with testing skills are considered part of the Developers, who are a cross-functional group with all the skills necessary to create a done Increment.

Furthermore, Scrum promotes collective ownership. The entire Scrum Team is accountable for creating a valuable, useful Increment each Sprint. This shared accountability means that quality is the responsibility of everyone on the team, not siloed to a specific role. The Developers are specifically accountable for instilling quality by adhering to the Definition of Done.

A. This suggests quality is the sole responsibility of a specific role, which contradicts Scrum's principle of collective ownership by the entire team.

B. Scrum does not have a "test manager" role. This describes a hierarchical structure that is antithetical to a self-managing Scrum Team.

C. This creates an adversarial relationship. In Scrum, team members collaborate to build quality in, rather than having one group inspect the work of another.

1. Schwaber

K.

& Sutherland

J. (2020). The Scrum Guide. Scrum.org.

Page 5: "The fundamental unit of Scrum is a small team of people

a Scrum Team. The Scrum Team consists of one Scrum Master

one Product Owner

and Developers. Within a Scrum Team

there are no sub-teams or hierarchies." (Supports option D)

Page 6: "The entire Scrum Team is accountable for creating a valuable

useful Increment every Sprint." (Supports option E)

Page 6: "Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint... The specific skills needed by the Developers are often broad and will vary with the domain of work." (Supports option D)

2. Dingsøyr

T.

Nerur

S.

Balijepally

V.

& Moe

N. B. (2012). A decade of agile methodologies: Towards explaining agile software development. Journal of Systems and Software

85(6)

1213-1221.

Section 3.1

Page 1215: The paper emphasizes that agile methods

including Scrum

rely on "cross-functional teams [that] have all the competencies needed to accomplish the work without depending on others not part of the team." This principle underpins the absence of a separate "Tester" role

as testing is a competency integrated within the team of Developers. (Supports option D)