“Work” refers to “tasks” in this context, which is totally up to the Development Team. They can add, remove, and change them as they wish, in contrast to the Product Backlog items selected for the Sprint, which are not changed during the Sprint.
There are two elements in the Sprint Backlog:
The items selected from the Product Backlog: we don’t change them after the Sprint Planning
The tasks created by breaking down the items: only a few of them are created in the Sprint Planning, and the rest will be created during the Sprint. Otherwise, it would be a form of upfront planning. Tasks are referred to as “work” or “plan” in the PSM I exam.
The Sprint Backlog is owned by the Development Team, and no one else is allowed to create or update it.
Ask the Product Owner to remove it
Inform the Product Owner, so that s/he can cancel the Sprint if the work is significant
Keep it, but inform the Product Owner
Just remove it
There are three problems with this statement:
The Scrum Master cannot order anyone to do something or prevent them from doing something. S/he can only convince them to do the right thing by training and coaching.
The Sprint Goal is composed by the whole Scrum Team, rather than by the Product Owner alone.
The Sprint Goal is composed during the Sprint Planning, rather than before it.
Scrum is an Agile (adaptive) framework, within which various processes and techniques should be used in right orchestration.
The project management activities are distributed among all three Scrum roles: the Product Owner, the Scrum Master, and the Development Team.
The Product Owner
The Development Team
The team leader(s)
The Scrum Master
选择要在Apple App Store上查看的Topgrade应用程序。