Each Scrum role has specific responsibilities in managing a Scrum project. Below, choose the role that is
correctly matched to its responsibility.
Product Owner - invites to a grooming session only those stakeholders whose feedback is required and
who can make final decisions about which suggested changes can be considered as Formal Change
Requests.
Scrum Master - ensures that the requirements and Acceptance Criteria are not altered during the Sprint
Review Meeting.
Stakeholders - incorporate new and modified features into the deliverables whenever possible.
Scrum Team - decide whether the change can wait until the next Sprint or represents an urgent situation
that may require ending the current Sprint and starting a new one.
Although the Stakeholder(s) and the Product Owner have the final say on Prioritized Product Backlog Items
and whether to accept or reject any Change Requests presented during Demonstrate and Validate Sprint, it is
the Scrum Master’s responsibility to ensure that the requirements and Acceptance Criteria are not altered
during the Sprint Review Meeting for the User Stories completed in the current Sprint. This prevents the
rejection of completed User Stories based on the fact that they do not meet newly changed requirements. If
any requirements need to be changed, any corresponding PBI needs to be revised to accommodate the
modified requirements in a future Sprint.
Submit