Which of the following about User Story Acceptance Criteria is true?

The Scrum Master acts as a servant-leader and facilitator for the Scrum Team. A primary responsibility is to protect the team from external disruptions and to ensure the Scrum framework is followed correctly. Changing the Acceptance Criteria of a User Story that the team has already committed to and is working on within a Sprint is a form of scope creep. This disrupts the team's focus and jeopardizes the Sprint Goal. Therefore, it is the Scrum Master's duty to coach the Product Owner and shield the team from such changes, ensuring the stability of the Sprint Backlog.

A. Acceptance Criteria are objective, measurable, and testable conditions that remove ambiguity from a User Story, not add subjectivity.

B. The Product Owner, not the Scrum Master, is responsible for formally accepting or rejecting completed User Stories during the Sprint Review meeting.

D. The goal is to maintain a stable Sprint Backlog. While the team must be aware of any negotiated changes, their primary responsibility is not just to "track" changes but to focus on the committed work. The Scrum Master's role is to prevent such disruptive changes in the first place.

---

1. A Guide to the Scrum Body of Knowledge (SBOK® Guide)

3rd Edition.

For Correct Answer (C): Section 4.3.2

Scrum Master’s Responsibilities. It states

"The Scrum Master is also responsible for shielding the team from any distractions or interruptions that could affect its focus on achieving the Sprint Goal." Changing acceptance criteria mid-sprint is a significant interruption.

For Incorrect Option (A): Section 6.2.2

Acceptance Criteria. It defines

"Well-defined Acceptance Criteria are objective... They are a set of guidelines that can be used to confirm that the User Story has been completed and is working as intended." This confirms they are objective

not subjective.

For Incorrect Option (B): Section 3.3.2

Product Owner’s Responsibilities. It clarifies

"The Product Owner is the only person responsible for accepting the deliverables that meet the User Story Acceptance Criteria." This role does not belong to the Scrum Master.

For Incorrect Option (D): Section 8.2.1

Sprint Execution. The principle of a stable Sprint Backlog is emphasized. While collaboration exists

the framework discourages mid-sprint changes to committed items to protect the Sprint Goal. The Scrum Master facilitates this stability.