How much time must a Product Owner spend with the Developers? (choose the best answer)
Correct Answer: A
The Product Owner must spend enough time with the Developers so that they are confident the Increment will meet the intended value. This is because: * The Developers are accountable for creating a "Done" Increment in every Sprint. They must ensure that every Product Backlog item they work on meets the Definition of Done before it is considered complete. * The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They must inspect the Increment at the end of each Sprint and assess how it delivers value and contributes to the Product Goal. * The Product Owner and the Developers must collaborate closely throughout the Sprint to ensure that * they have a shared understanding of what they are building and why. The Product Owner must provide clarifications, feedback, and guidance to the Developers as needed to help them create a valuable Increment. * The amount of time that the Product Owner must spend with the Developers may vary depending on the context, complexity, and uncertainty of the product development. However, it should be enough so that both parties are confident that the Increment will meet the intended value. Other options, such as 40%, as much time as the Developers tell them to be present, or 100%, are not valid answers as they imply a fixed or arbitrary amount of time that does not reflect the actual needs and dynamics of the product development. References: * [Scrum Guide], page 7, section "Developers" * [Scrum Guide], page 6, section "Product Owner" * [Scrum Guide], page 10, section "Definition of Done" * [Scrum Guide], page 10, section "Increment" * [Scrum Guide], page 10, section "Product Goal"
Question 32
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
Correct Answer: B
Question 33
Who is accountable for creating a valuable and usable Increment each Sprint? (choose the best answer)
Correct Answer: A
Explanation The Scrum Team member who is accountable for creating a valuable and usable Increment each Sprint is the Developers. This is because: * The Developers are accountable for creating a "Done" Increment in every Sprint. They must ensure that every Product Backlog item they work on meets the Definition of Done before it is considered complete. * The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It is a shared understanding among the Scrum Team and the stakeholders of what "Done" means for any Product Backlog item that is selected for a Sprint. * The Increment is a concrete and usable outcome of the Sprint that provides a measure of progress and value delivery. It must be in useable condition regardless of whether it will be released or not. * The Developers are self-managing professionals who organize and manage their own work. They decide how to best accomplish their work, rather than being directed by others outside the Scrum Team. Other options, such as the CEO, the Product Owner, the Scrum Master, or the Scrum Team, are not accountable for creating a valuable and usable Increment each Sprint. They may have different roles and accountabilities in Scrum, but they do not do the actual work of creating a "Done" Increment. References: * [Scrum Guide], page 7, section "Developers" * [Scrum Guide], page 10, section "Definition of Done" * [Scrum Guide], page 10, section "Increment" * [Scrum Guide], page 7, section "The Scrum Team"
Question 34
What are the two responsibilities of testers in a Scrum Team? (choose the best two answers)
Correct Answer: B,D
Explanation Scrum is a framework for developing, delivering, and sustaining complex products. Scrum defines three roles: the Product Owner, the Scrum Master, and the Developers. Scrum does not have any other roles or titles, such as "tester", "analyst", "designer", or "architect". The Developers are the people in the Scrum Team who are accountable for creating a "Done" Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations. The Developers are responsible for quality, not just for programming. Quality is not something that can be added or verified after the product is built. Quality is something that must be built into the product from the start, by following good practices, standards, and principles. Quality is also something that must be inspected and adapted continuously, by applying feedback loops, testing methods, and improvement actions. The Developers are not divided into sub-teams or sub-roles based on their skills or specialties. The Developers are a cross-functional and self-organizing team that has all the skills and capabilities needed to create a valuable product Increment. The Developers collaborate and coordinate their work as one unit, without any hand-offs or silos. The Developers may have different backgrounds or expertise, such as testing, analysis, design, or architecture. However, these are not separate roles or responsibilities in Scrum. They are part of the collective accountability and responsibility of the Developers as a whole. The Developers may perform different tasks or activities based on their skills or preferences, but they are all equally responsible for delivering a high-quality product Increment. References: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum Quality: https://www.scrum.org/resources/blog/quality-scrum-value
Question 35
Who determines when it is appropriate to update the Sprint Backlog during a Sprint? (choose the best answer)
Correct Answer: C
Explanation The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint, and it belongs solely to the Developers. The Developers are accountable for creating a "Done" Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations. The Developers are also responsible for updating the Sprint Backlog throughout the Sprint. The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum. The Developers modify the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Developers work through the plan and learn more about the work needed to achieve the Sprint Goal. As new work is required, the Developers add it to the Sprint Backlog. As work is performed or completed, the estimated remaining work is updated. When elements of the plan are deemed unnecessary, they are removed. Only the Developers can change its content and order during a Sprint. References: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Sprint Backlog: https://www.scrum.org/resources/what-is-a-sprint-backlog Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
