True or False: During the Sprint Review the stakeholder's role is to reorder the Product Backlog.
During the Sprint Review, the stakeholder's role is not to reorder the Product Backlog, but rather to provide feedback and suggestions on the product and the process. Therefore, the answer is false because:
The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration. The stakeholders are invited to attend the Sprint Review as observers, participants, or customers, and they can share their opinions, ideas, or requests regarding the product and its features, functionality, quality, value, etc.
The ordering of the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions. The Product Owner may consider the feedback and suggestions from the stakeholders, as well as other factors such as dependencies, risks, costs, etc., when ordering the Product Backlog. However, they are not obliged to follow or implement them.
The Product Backlog is not a fixed or final list of requirements, but rather an emergent and dynamic artifact that represents all the possible changes to the product. The Product Owner is accountable for effective Product Backlog management, which includes refining, communicating, and optimizing the Product Backlog items. The Product Owner may update the Product Backlog at any time, not only during the Sprint Review.
Scrum Guide 2020, page 11: ''The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner.''
Scrum Guide 2020, page 11: ''The Product Owner is accountable for effective Product Backlog management, which includes ... ordering Product Backlog items; and ensuring that the Product Backlog is transparent, visible and understood.''
Scrum Guide 2020, page 15: ''The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration.''
The Scrum Master observes the Product Owner struggling with ordering the Product Backlog.
What is an appropriate action for the Scrum Master to take?
(choose the best answer)
Who can cancel a Sprint?
(choose the best answer)
The Product Owner is the sole person responsible for managing the Product Backlog and ensuring that the value of the work the Scrum Team performs is understood by everyone involved. The Product Owner is the only person who can cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master1. A Sprint can be cancelled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master. A Sprint would be cancelled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be cancelled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense1. Reference:
Scrum Guide
Sprint Cancellation
Can Scrum Master cancel a sprint?
During a Sprint, when is new work or further decomposition of work added to the Sprint
Backlog?
(choose the best answer)
New work or further decomposition of work is added to the Sprint Backlog as soon as possible after it is identified because:
It reflects the current state of the Sprint. The Sprint Backlog is a plan that the Developers create and update throughout the Sprint, based on their progress, learnings, and changes. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can ensure that the Sprint Backlog is transparent, accurate, and up-to-date.
It enables the Developers to self-manage their work. The Developers are accountable for organizing and managing their own work, and they have the authority to change the Sprint Backlog as needed. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can exercise their autonomy and empowerment, and adjust their plan accordingly.
It supports the achievement of the Sprint Goal. The Sprint Goal is a single objective that provides guidance and focus for the Developers throughout the Sprint. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can ensure that their work is aligned with and contributes to the Sprint Goal.
Scrum Guide 2020, page 6: ''Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.''
Scrum Guide 2020, page 6: ''The Developers are accountable for ... organizing and managing their work.''
Scrum Guide 2020, page 10: ''The Sprint Goal is a single objective for the Sprint.''
Scrum Guide 2020, page 14: ''The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current Definition of Done.''
Scrum Guide 2020, page 14: ''The Sprint Backlog is composed of ... all of the work needed to deliver a product Increment that meets the Definition of Done.''
Scrum Guide 2020, page 14: ''The Developers can change the content of the Sprint Backlog throughout the Sprint as more is learned.''
Developers are self-managing, which of the following do they manage?
(choose the best answer)
Developers are self-managing, which means that they decide how much work they can do in a Sprint, and how they will do it1. They manage the Sprint Backlog, which is the plan for how the Developers will achieve the Sprint Goal, and the single source of truth for the work to be done in the Sprint2. The Developers create and update the Sprint Backlog throughout the Sprint as more is learned[3][3]. The other options are not managed by the Developers, but by the Product Owner or the Scrum Team as a whole. The Product Owner is accountable for ordering the Product Backlog, which is an ordered list of everything that is known to be needed in the product4. The Product Owner also decides when to release the product, based on the value, risk, and stakeholder feedback5. The Scrum Team collaborates on inviting the stakeholders for the Sprint Review, which is an event where the Scrum Team and the stakeholders inspect the product Increment and adapt the Product Backlog. The Scrum Team also decides the Sprint length, which is the time-box within which the Scrum Team delivers a product Increment.
1: The Scrum Guide, November 2020, p. 6
2: The Scrum Guide, November 2020, p. 10
[3][3]: The Scrum Guide, November 2020, p. 10
4: The Scrum Guide, November 2020, p. 6
5: Managing Products with Agility, Scrum.org, accessed on December 16, 2023
: The Scrum Guide, November 2020, p. 13
: The Scrum Guide, November 2020, p. 9
Sandra Nelson
10 days agoBetty Morris
21 days agoTimothy Stewart
14 days agoAmy Gonzalez
17 days agoGeorge Nelson
6 days agoGeorge Mitchell
2 days agoSabra
1 month agoRenato
2 months agoVirgie
2 months agoEileen
2 months agoGolda
2 months agoTayna
3 months agoLezlie
3 months agoVerda
3 months agoTamra
3 months agoGlory
4 months agoStevie
4 months agoAhmed
4 months agoSabina
4 months agoMignon
5 months agoNaomi
5 months agoDoretha
5 months agoBette
6 months agoHuey
6 months agoRima
6 months agoJulian
6 months agoLynelle
7 months agoViola
7 months agoWillard
7 months agoSylvia
7 months agoSalley
8 months agoBette
8 months agoIlda
8 months agoStevie
8 months agoAzalee
10 months agoMelina
11 months agoKanisha
1 year agoDenny
1 year agoKiley
1 year agoHorace
1 year agoRodrigo
1 year agoJanet
1 year agoMose
1 year agoKasandra
1 year agoLasandra
1 year agoDella
1 year agoGary
2 years agoDeangelo
2 years agoJolanda
2 years agoTruman
2 years agoIvory
2 years agoFelice
2 years agoFrank
2 years agoJulieta
2 years agoDominga
2 years agoLezlie
2 years agoMelda
2 years agoIvette
2 years agoKeshia
2 years agoWinifred
2 years agoLynelle
2 years ago