Change Scope
What is the best practice attitude for Scrum Master or Development Team, if Product Owner change the scope of User Story or enlarge the Test Cases during Sprint Execution ?
The Scrum Guide says “Only the Development Team can change its Sprint Backlog during a Sprint.”
Do the user stories and test cases you refer to constitute work which has been planned into the Sprint Backlog?
And, if the user stories need to change because the Sprint Goal becomes obsolete, the Product Owner should consider cancelling the Sprint. Then those user stories should be discussed in the next Sprint Planning.
User stories or acceptance criteria should not be changed and as a scrum master you should not allow this to happen.
There must be an escalation matrix your org must be following.
Hi All,
Appreciate for your feedbacks.. I am also agree on that Acceptance Criteria can not be enlarge and User Story scope can be change
>> There must be an escalation matrix your org must be following.
How might something like an escalation matrix detract from self organization? Shouldn't a self organized team be able to work through this themselves?