True or False: Product Owners must specify complete acceptance criteria for a Product Backlog item before the Developers can select the item in Sprint Planning.
Correct Answer: B
answer: False Very Short Explanation: According to Scrum.org, the Product Owner is not required to create clear and unambiguous acceptance criteria for each item in the product's backlog before it can be selected in Sprint Planning1. Acceptance Criteria is optional and is not prescribed by Scrum12. It can be valuable, but it's not a must12. The Developers can inspect and adapt the Sprint Backlog in any way they see fit, in order to help meet the Sprint Goal2.
Question 32
The Scrum Master is accountable for ensuring that the Product Backlog is transparent, visible and understood.
Correct Answer: B
Question 33
Does it replace the importance of empiricism in Scrum to forecast the Sprint progress using burn-down charts?
Correct Answer: A
Question 34
True or False: An Increment must be released to customers or users at the end of each Sprint.
Correct Answer: B
* An Increment is a concrete stepping stone toward the product vision. It is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be "Done", which means it meets the Definition of Done and is usable. * The Scrum Team decides when and how to release an Increment to customers or users. The Product Owner is responsible for maximizing the value of the product and the work of the Developers, and may decide to release an Increment at any time during or after a Sprint. The Developers are responsible for creating a potentially releasable Increment each Sprint, and may collaborate with the Product Owner and the stakeholders to determine the best way to deliver value. * Releasing an Increment to customers or users is not mandatory at the end of each Sprint. The Scrum Team may choose to release an Increment more or less frequently, depending on the product goals, market conditions, customer feedback, or technical feasibility. However, releasing an Increment regularly can provide many benefits, such as: * Validating assumptions and hypotheses about the product value and quality. * Obtaining feedback and data from real users and customers. * Increasing customer satisfaction and loyalty. * Reducing risks and uncertainties. * Improving transparency and collaboration. References: * Scrum Guide: https://www.scrumguides.org/scrum-guide.html * Increment: https://www.scrum.org/resources/what-is-an-increment * Releasing Value: https://www.scrum.org/resources/blog/releasing-value
