SMC practice question 1 of 25

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

Full set: 148 questions

Domain Plan and Estimate Phase

Answer options
A: User Stories are objective, and the Acceptance Criteria provides the subjectivity required for the User Story to be considered as Done.
B: In the Sprint Review Meetings, the Acceptance Criteria provides the context for the Scrum Master to decide if a User Story has been completed satisfactorily.
C: It is the Scrum Master who has to ensure that the Acceptance Criteria for a User Story are not changed by the Product Owner in the middle of a Sprint. Correct answer
D: It is the Scrum Team's responsibility to keep track of what changes are being made to the Acceptance Criteria even during the Sprint.
Correct Answer:
C. It is the Scrum Master who has to ensure that the Acceptance Criteria for a User Story are not changed by the Product Owner in the middle of a Sprint.
Explanation

The Scrum Master's role includes protecting the Scrum Team from outside interruptions and ensuring the Scrum process is followed. A key aspect of this is safeguarding the Sprint Goal and the Sprint Backlog once a Sprint has begun. While the Product Owner defines and clarifies Acceptance Criteria, changing them mid-sprint constitutes scope creep, which can jeopardize the Sprint Goal. The Scrum Master facilitates communication and coaches the Product Owner on the importance of keeping the Sprint scope stable.

Why Incorrect

A. Acceptance Criteria are objective, testable conditions that a User Story must meet to be considered "Done," removing subjectivity.
B. The Product Owner, not the Scrum Master, is responsible for accepting or rejecting completed User Stories during the Sprint Review Meeting.
D. The Scrum Team should not be expected to accommodate changes to Acceptance Criteria during a Sprint; the goal is to maintain a stable scope.

References

1. ScrumStudy. (2017). A Guide to the Scrum Body of Knowledge (SBOK® Guide) (3rd ed.). Section 3.5.1.1, Page 70. "The Scrum Master guides, facilitates, and teaches Scrum practices to everyone involved in the project; clears impediments for the team; and ensures that Scrum processes are being followed."

2. ScrumStudy. (2017). A Guide to the Scrum Body of Knowledge (SBOK® Guide) (3rd ed.). Section 8.6, Page 210. "The Product Owner reviews the product increment against the Acceptance Criteria for each User Story in the Sprint Backlog to determine whether it is acceptable."

3. ScrumStudy. (2017). A Guide to the Scrum Body of Knowledge (SBOK® Guide) (3rd ed.). Section 6.4, Page 134. "Acceptance Criteria are objective; therefore, a User Story is either done or not done. There is no partial completion."

Scroll to Top