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.
Which two things should the Scrum Team do during the first Sprint? (choose the best two answers)
Correct Answer:DE
the first Sprint is the same as any other Sprint, and the Scrum Team should deliver a potentially releasable Increment of "Done" product at its conclusion. This means that the team should build at least one piece of valuable functionality that meets the Definition of Done and aligns with the Sprint Goal. The other options are not things that the Scrum Team should do during the first Sprint, as they are either too detailed, too vague, or too long-term for the Scrum framework. The Scrum Team should not make up a plan for the rest of the project, as Scrum is an empirical process that adapts to changing requirements and feedback1. The Scrum Team should not define the major product features and a release plan architecture, as these are the responsibilities of the Product Owner, who should have a vision and a roadmap for the product2. The Scrum Team should not analyze, describe, and document the requirements for the subsequent Sprints, as this would violate the principle of emergent design and just-in-time planning3.
1: The Scrum Guide | Scrum.org 2: What is a Product Owner? | Scrum.org 3: Emergent Design and Just-in-Time Planning | Scrum.org
True or False: Multiple Scrum Teams working on the same product or system all select work
from the same Product Backlog.
Correct Answer:A
For the purpose of transparency, when does Scrum say a valuable and useful Increment must
be available?
(choose the best answer)
Correct Answer:A
The Scrum Guide states that "The Increment 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 must be in useable condition and meet the Scrum Team’s definition of ‘Done.’"1 This means that a valuable and useful Increment must be available at the end of every Sprint, regardless of the release frequency or the Product Owner’s request. This ensures transparency, feedback, and continuous improvement.
References:
✑ 1: The Scrum Guide2, page 14
✑ 2: The Scrum Guide
What are the two responsibilities of testers in a Scrum Team? (choose the best two answers)
Correct Answer:BD
✑ 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