At the end of a Sprint, a Product Backlog item worked on during the Sprint does not meet the Definition of Done. What two things should happen with the undone Product Backlog item? (choose the best two answers)
Correct Answer: C,D
According to the Scrum Guide, if a Product Backlog item does not meet the Definition of Done, it should not be included in the Increment for the Sprint1. The item is considered unfinished and therefore cannot be part of the Increment that may be released or presented as 'Done'. The undone work should be re-estimated and put back on the Product Backlog for the Product Owner to prioritize for future Sprints2. This ensures transparency and maintains the integrity of the Increment's quality. References: The Scrum Guide provides clear guidance on handling undone work and emphasizes the importance of the Definition of Done as a quality standard for the Increment1. The Professional Scrum Product Owner™ (PSPO I) materials also align with this approach, underscoring the Product Owner's role in managing the Product Backlog and ensuring that only 'Done' items are considered for release
Question 157
Which two questions are answered by the Sprint Planning?
Correct Answer: A,B
Question 158
A Product Backlog is: (choose the best three answers)
Correct Answer: B,C,D
A Product Backlog is: Managed by the Product Owner. The Product Owner is the sole person responsible for managing the Product Backlog, which is an emergent, ordered list of what is needed to improve the product. They must ensure that the Product Backlog is transparent, visible, and understood by everyone who needs to work on it. An inventory of things to be done for the Product. The Product Backlog contains all the features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases. The Product Backlog items have a description, an order, an estimate, and a value. Ordered based on priority, value, dependencies, and risk. The Product Owner orders the Product Backlog items based on various factors that affect their importance and urgency for the product. These may include customer needs, business value, stakeholder feedback, technical dependencies, or market opportunities. Other options, such as an exhaustive list of upfront approved requirements to be implemented or only visible to the Product Owner and stakeholders, are not valid descriptions of a Product Backlog. They may reflect a misunderstanding of what a Product Backlog is or how Scrum works. Reference: [Scrum Guide], page 6, section "Product Owner" [Scrum Guide], page 11, section "Product Backlog" [Professional Scrum Product Owner Training], page 7, section "Product Backlog Management"
Question 159
The Product Owner is not available and cannot answer the developers questions before the Sprint Planning. Therefore, the developers feel a high level of uncertainty to make a reliable forecast . What should the team do?
Correct Answer: B
Question 160
The Developers can change the Sprint scope on their own as more is learned.
