True or False: Product Owners must create clear and unambiguous acceptance criteria for each Product Backlog item before it may be selected in Sprint Planning.
Correct Answer: B
Explanation It is not true that a Product Owner must create clear and unambiguous acceptance criteria for each Product Backlog item before it may be selected in Sprint Planning. This is because: * Acceptance criteria are a set of conditions that a Product Backlog item must satisfy to be accepted by the Product Owner or the stakeholders. They are used to verify that the item meets the expected quality and value standards. * Acceptance criteria are not mandatory or prescribed in Scrum. They are one of the possible techniques * that a Product Owner may use to communicate their expectations and requirements to the Developers and the stakeholders. They are not part of the Scrum Guide or the Definition of Done. * Acceptance criteria do not need to be created before Sprint Planning. They can be created or refined at any time during the product development process, as long as they are clear and agreed upon before the item is considered complete. They can also be changed or updated based on feedback or new insights. * The only requirement for a Product Backlog item to be selected in Sprint Planning is that it is sufficiently clear and ready for selection. This means that it has enough detail and precision for the Developers to understand what they are supposed to build and why. It also means that it has been refined and ordered by the Product Owner based on value and impact. References: * [Scrum Guide], page 14, section "Sprint Planning" * [Scrum Guide], page 12, section "Product Backlog Refinement" * [Professional Scrum Product Owner Training], page 7, section "Product Backlog Management"
Question 102
True or False: Cross-functional teams are optimized to work on one component or layer of a system only.
Correct Answer: B
Cross-functional teams are not optimized to work on one component or layer of a system only. This is because: Cross-functional teams are teams that have all the skills and competencies needed to accomplish the work without depending on others who are not part of the team. Cross-functional teams are able to deliver value across the entire product, rather than focusing on a specific component or layer. They can work on any aspect of the product that is needed to achieve the Sprint Goal and the Product Goal. Cross-functional teams are more agile, collaborative, and creative than teams that are specialized or siloed. They can reduce dependencies, handoffs, and delays, and increase feedback, learning, and adaptation. Reference: [Scrum Guide], page 7, section "Developers" [Scrum Guide], page 10, section "Product Goal" [Scrum Guide], page 7, section "The Scrum Team"
Question 103
Which are characteristics of the Daily Scrum? (choose the best two answers)
Correct Answer: B,D
the Daily Scrum is a 15-minute event for the Developers of the Scrum Team that is held at the same time and place every working day of the Sprint. The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work1. The other options are not characteristics of the Daily Scrum, as it is not facilitated by the team lead, it does not consist of the Scrum Master asking the team for status, it is not held first thing in the morning, and it is not free form and designed to promote conversation234. 1: What is a Daily Scrum? | Scrum.org 2: What Is the Daily Scrum? | A Guide to the Daily Event - Scrum Alliance 3: What is Daily Scrum? | VivifyScrum 4: Daily Scrum | Definition and Overview - ProductPlan
Question 104
Who determines how work is performed during the Sprint? (choose the best answer)
Correct Answer: D
Explanation The Developers are the people in the Scrum Team who are committed to creating any aspect of a usable Increment each Sprint. The Developers are accountable for organizing and managing their work. Only the Developers can decide how to perform the work during the Sprint1. The Developers plan the work necessary to create an Increment that meets the Definition of Done during the Sprint Planning event. This is often done by decomposing Product Backlog items into smaller work items of one day or less. How this is done is at the sole discretion of the Developers2. The Developers also inspect their progress toward the Sprint Goal and adapt their plan during the Daily Scrum1. The Developers are self-managing, which means they decide internally who does what, when, and how1. The Scrum Master, the Product Owner, the team manager, and the subject matter experts are not involved in determining how the work is performed during the Sprint. They may provide guidance, feedback, or support, but they do not interfere with the Developers' autonomy and accountability134. References: * Scrum Guide * What is a Developer? * Who Determines How Work Is Performed During The Sprint? * What is Sprint Planning?
