When does a Developer become accountable for the value of a Product Backlog item selected for the Sprint?
(choose the best answer)
Correct Answer:
D
According to the Scrum Guide, the Scrum Team consists of one Product Owner, one Scrum Master, and Developers. The Scrum Team is responsible for all product-related activities, including delivering a valuable, usable product increment every Sprint. The Product Owner is accountable for maximizing the value of the product and the work of the Developers. The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog; instilling quality by adhering to a Definition of Done; and adapting their plan each day toward the Sprint Goal. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, helping everyone understand Scrum theory and practice, and removing impediments to the Scrum Team’s progress.
Therefore, the Developers are not individually accountable for the value of a Product Backlog item selected for the Sprint, but collectively accountable as part of the Scrum Team. The value of a Product Backlog item is determined by the Product Owner, who orders the Product Backlog items based on stakeholder needs and feedback. The Developers collaborate with the Product Owner to understand the value and requirements of each Product Backlog item and deliver a potentially releasable product increment that meets the Definition of Done and the Sprint Goal.
References:
✑ [Scrum Guide], section 2.2: “The Scrum Team is responsible for all product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else that might be required.”
✑ Accountabilities in Scrum | Scrum.org: “Scrum has three accountabilities, each with a different focus : Product Owner (green figure) The "What". With a focus on Value, time to market, return on investment and Total Cost of Ownership (TCO). Developers (red figures) The "How". Focus on building something that is Done – that the increment is useable and potentially releasable.”
✑ What is a Developer in Scrum? | Scrum.org: “The specific skills needed by the Developers are often broad and will vary based on the type of work they are doing. However, the Developers are always accountable for: Creating a plan for the Sprint, the Sprint Backlog Instilling quality by adhering to a Definition of Done Adapting their plan each day toward the Sprint Goal”
What is the purpose of a Sprint Review? (choose the best answer)
Correct Answer:
C
✑ The Sprint Review is an event that occurs at the end of each Sprint, where the Scrum Team and the stakeholders inspect the Increment and adapt the Product Backlog if needed. The Sprint Review is an opportunity for the Product Owner to validate that the Increment meets their expectations and delivers value to the customers and users. The Sprint Review is also an opportunity for the Developers to demonstrate their work and receive feedback from the Product Owner and the stakeholders.
✑ The purpose of a Sprint Review is to inspect the product Increment with the stakeholders and collect feedback on next steps. The Sprint Review is a collaborative and interactive session where the Scrum Team and the stakeholders discuss what was done in the Sprint, what problems were encountered, what was learned, and what can be improved or changed. The Sprint Review also provides input for updating the Product Backlog to maximize value in future Sprints.
✑ The other options are not valid or relevant purposes of a Sprint Review. They are either too vague, unrelated, or incorrect. They are:
References:
✑ Scrum Guide: https://www.scrumguides.org/scrum-guide.html
✑ Sprint Review: https://www.scrum.org/resources/what-is-a-sprint-review
If Product Backlog refinement is needed, when is the ideal time for refinement to take place and
who should participate? (choose the best two answers)
Correct Answer:
AE
The ideal time for refinement to take place and who should participate are the Scrum Team during the current Sprint, if they have been unable during preceding Sprints to define Product Backlog items with enough precision to begin work, and the Scrum Team on an ongoing basis, defining Product Backlog items into smaller more precise items that are ready for selection. This is because:
✑ Product Backlog refinement is the act of adding detail, estimates, and order to Product Backlog items. It is an ongoing and collaborative process that involves the whole Scrum Team.
✑ The Scrum Team should refine the Product Backlog as needed to ensure that there are enough items that are sufficiently clear and ready for selection in Sprint Planning. The amount of time spent on refinement usually varies from one Scrum Team to another, but it is recommended not to exceed 10% of the capacity of the Developers.
✑ The Scrum Team may also use a Sprint to refine the Product Backlog if they have not been able to do so in previous Sprints. This may happen when the product is new or complex, or when there is a significant change in the product vision or direction. However, this should be an exception rather than a rule, as it may delay the delivery of value and feedback.
Other options, such as business analysts doing the refinement work for the Scrum Team, the Product Owner doing the refinement alone in Sprint 0 or between Sprints, or handing off the ownership of the Product Backlog to someone else, are not consistent with the principles and values of Scrum. They may lead to misunderstandings, misalignment, or loss of ownership and accountability.
References:
✑ [Scrum Guide], page 11, section “Product Backlog”
✑ [Scrum Guide], page 12, section “Product Backlog Refinement”
✑ [Professional Scrum Product Owner™ Training], page 7, section “Product Backlog Management”
✑ [Professional Scrum Product Owner™ Training], page 8, section “Release Management”
✑ [Professional Scrum Product Owner™ Training], page 9, section “Business Strategy”
As the Developers start work during the Sprint, they realize they have selected too much work to finish in the Sprint. What should they do?
(choose the best answer)
Correct Answer:
B
This is the best answer because it respects the Scrum values of openness, commitment, and focus. The Developers should be transparent about their progress and collaborate with the Product Owner to adjust the Sprint scope accordingly. The Product Owner is responsible for maximizing the value of the product and the work of the Developers, so he or she should be involved in any decisions that affect the Sprint Goal and the Product Backlog. References:
✑ Scrum Guide, page 10: “If the work turns out to be different than the Developers expected, they collaborate with the Product Owner to negotiate the scope of Sprint Backlog within the Sprint.”
✑ Scrum Guide, page 11: “The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.”
The timebox for a Daily Scrum is? (choose the best answer)
Correct Answer:
D
The Scrum Guide states that "The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours."1 The Daily Scrum is a quick and simple planning meeting designed to keep everyone in the loop with how other team members are getting on. It ensures that team members are fully aligned with each other and on track to hit the Sprint Goal. References:
✑ 1: The Scrum Guide2, page 11
✑ 2: The Scrum Guide
