Which of the following about User Story Acceptance Criteria is true?
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.
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.
Answer: C
Explanation:
User Story is Done according to the agreed upon Acceptance Criteri A. Thus, the role of Acceptance Criteria in maintaining quality is critical and needs to be clearly understood by the team. It is the responsibility of the
Scrum Master to ensure that the Acceptance Criteria for a User Story are not changed by the Product Owner in the middle of a Sprint. Partially completed User Stories are rejected as not Done and moved back into the Prioritized Product Backlog.
Explanation:
Reference: http://blog.scrumstudy.com/scrumstudy-scrum-video-on-acceptance-criteria-and-prioritizedproduct-backlog/