Skip to main content

Due to the Russian invasion of Ukraine, we have paused all purchases and training in and from Russia.

Change Scope

Last post 01:02 pm May 28, 2018 by Chris Belknap
5 replies
03:30 pm May 24, 2018

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 ? 

04:15 pm May 24, 2018

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?

04:26 pm May 24, 2018

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.

08:29 am May 25, 2018

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.

12:36 pm May 28, 2018

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

01:02 pm May 28, 2018

>> 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?