In the Daily Scrum, the Scrum Master is not allowed to attend.
Correct Answer: A
Question 2
How much of the Sprint Backlog must be defined during the Sprint Planning event? (choose the best answer)
Correct Answer: B
D. Just enough tasks for the Scrum Master to be confident in the Developers' understanding of the Sprint. Explanation: The amount of the Sprint Backlog that must be defined during the Sprint Planning event is enough so the Developers can create their forecast of what work they can do. This is because: Sprint Planning is an event where the Scrum Team plans for the upcoming Sprint. The purpose of Sprint Planning is to align the entire Scrum Team around a common goal and a plan for delivering an Increment that meets that goal. The Developers are accountable for creating a Sprint forecast, which is a selection of Product Backlog items that they intend to work on during the Sprint. The Sprint forecast should be realistic, achievable, and valuable. The Developers are also accountable for creating a plan for how they will deliver the selected Product Backlog items as a "Done" Increment. The plan may include tasks, dependencies, risks, estimates, or other information that helps them organize and manage their work. The amount of the Sprint Backlog that must be defined during Sprint Planning may vary depending on the context, complexity, and uncertainty of the product development. However, it should be enough so that the Developers can create their forecast of what work they can do and have a clear direction for the first few days of the Sprint. Other options, such as just enough to understand design and architectural implications, the entire Sprint Backlog being identified and estimated by the end of Sprint Planning, or just enough tasks for the Scrum Master to be confident in the Developers' understanding of the Sprint, are not valid answers as they do not reflect what must be defined during Sprint Planning or what is required for creating a Sprint forecast. Reference: [Scrum Guide], page 14, section "Sprint Planning" [Scrum Guide], page 7, section "Developers" [Scrum Guide], page 15, section "Sprint Backlog" [Scrum Guide], page 14, section "Sprint Planning"
Question 3
A Scrum Team is required to deliver a done Increment by the end of a Sprint. Select two statements that explain what done means. (choose the best two answers)
Correct Answer: A,D
A Scrum Team is required to deliver a done Increment by the end of a Sprint. Done means: No work is left to meet the Definition of Done. The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It is a shared understanding among the Scrum Team and the stakeholders of what it means for work to be complete. It may include criteria such as coding standards, testing, documentation, security, performance, etc. If a Product Backlog item or an Increment does not meet the Definition of Done, it cannot be released or presented at the Sprint Review. Ready to be released to end users. The Increment is a concrete output of the Sprint that adds value to the product. It is a potentially releasable functionality that adheres to the Scrum Team's current Definition of Done. It is not necessarily released at the end of each Sprint, but it must be in a state that allows for immediate release if the Product Owner decides so. The Increment should also align with the Sprint Goal and the Product Goal, and satisfy the needs and expectations of the customers and stakeholders. Reference: Scrum Guide 2020, page 10: "The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product." Scrum Guide 2020, page 10: "The moment a Product Backlog item meets the Definition of Done, an Increment is born." Scrum Guide 2020, page 14: "The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current Definition of Done."
Question 4
A Scrum Team is required to deliver a done Increment by the end of a Sprint. Select two statements that explain what done means. (choose the best two answers)
Correct Answer: A,D
A Scrum Team is required to deliver a done Increment by the end of a Sprint. Done means: * No work is left to meet the Definition of Done. The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It is a shared understanding among the Scrum Team and the stakeholders of what it means for work to be complete. It may include criteria such as coding standards, testing, documentation, security, performance, etc. If a Product Backlog item or an Increment does not meet the Definition of Done, it cannot be released or presented at the Sprint Review. * Ready to be released to end users. The Increment is a concrete output of the Sprint that adds value to the product. It is a potentially releasable functionality that adheres to the Scrum Team's current Definition of Done. It is not necessarily released at the end of each Sprint, but it must be in a state that allows for immediate release if the Product Owner decides so. The Increment should also align with the Sprint Goal and the Product Goal, and satisfy the needs and expectations of the customers and stakeholders. References: * Scrum Guide 2020, page 10: "The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product." * Scrum Guide 2020, page 10: "The moment a Product Backlog item meets the Definition of Done, an Increment is born." * Scrum Guide 2020, page 14: "The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current Definition of Done."
Question 5
Which of the following is required by Scrum? (choose the best answer)
Correct Answer: A
The Sprint Retrospective is one of the five events defined by Scrum. It is a formal opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The purpose of the Sprint Retrospective is to adapt the way of working so that it becomes more effective and enjoyable. The other options are not required by Scrum, but may be useful practices depending on the context. Developers do not have to stand up at the Daily Scrum, they can choose any format that works for them. A Sprint Burndown Chart is a common way to visualize the remaining work in a Sprint, but it is not mandated by Scrum. Release Planning is a topic that falls under the broader competency of Managing Products with Agility, but it is not a prescribed event in Scrum. The Scrum Guide Understanding and Applying the Scrum Framework Professional Scrum Product Owner™ I Certification
