True or False: The Product Owner must write all of the Product Backlog items (e.g., user stories, requirements, etc.) on the Product Backlog before handing them over to the Scrum Team.
Correct Answer: B
It is not true that the Product Owner must write all of the Product Backlog items (e.g. user stories, requirements, etc.) on the Product Backlog before handing them over to the Scrum Team. This is because: The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is never complete and constantly changes to reflect the needs and desires of the customers, users, and stakeholders. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for identifying and articulating the Product Goal, which is a long-term objective for the product that guides all the activities of the Scrum Team. The Product Owner is also accountable for managing the Product Backlog items effectively. They must ensure that they are transparent, visible, and understood by everyone who needs to work on them. They must also collaborate with the Developers and stakeholders to refine, order, and prioritize them based on value and impact. The Product Owner does not need to write all of the Product Backlog items by themselves or before handing them over to the Scrum Team. They can involve others in creating or contributing to them, such as customers, users, stakeholders, or Developers. They can also add or modify them at any time during the product development process, as long as they are clear and ready for selection in Sprint Planning. Reference: [Scrum Guide], page 6, section "Product Owner" [Scrum Guide], page 11, section "Product Backlog" [Scrum Guide], page 10, section "Product Goal" [Scrum Guide], page 12, section "Product Backlog Refinement" [Scrum Guide], page 14, section "Sprint Planning"
Question 7
Which statement best describes Scrum? (choose the best answer)
Correct Answer: C
* The best statement that describes Scrum is: A framework to generate value through adaptive solutions for complex problems. * Scrum is a lightweight framework that helps people, teams, and organizations to deliver valuable products in complex and uncertain environments. * Scrum is based on empiricism, which means that knowledge comes from experience and making decisions based on what is observed. Scrum employs an iterative and incremental approach to optimize predictability and control risk. * Scrum is not a defined and predictive process, a complete methodology, or a cookbook that defines best practices. Scrum provides the minimal boundaries within which teams can self-organize and create innovative solutions. References: Scrum Guide, Section 1 (Definition of Scrum) and Section 2 (Uses of Scrum)
Question 8
When should the Product Owner update the project plan? (choose the best answer)
Correct Answer: B
Explanation: The Product Owner is responsible for managing and refining the Product Backlog, which is the single source of truth for the plan of the product development. The Product Backlog is a living artifact that changes as the product and the market evolve. The Product Owner updates the Product Backlog continuously based on feedback, learning, and stakeholder needs. There is no separate project plan document in Scrum. References: * [Scrum Guide], section 3.1: "The Product Backlog is an emergent, ordered list of what is needed to improve the product." * [Professional Scrum Product Owner], chapter 5: "The Product Backlog represents everything necessary to develop and launch a successful product." * [What is a Product Backlog?]: "The Product Backlog is a list of all things that need to be done within the project."
Question 9
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
