The length of a Sprint should be: (choose the best answer)
Correct Answer: D
* The length of a Sprint is the timebox within which the Scrum Team creates a potentially releasable product Increment. The Sprint is a container for all the other Scrum events, such as the Sprint Planning, the Daily Scrum, the Sprint Review, and the Sprint Retrospective. The Sprint is also a feedback loop that allows the Scrum Team and the stakeholders to inspect and adapt the product and the process. * The length of a Sprint should be no more than one calendar month. This is the maximum duration allowed by Scrum, as longer Sprints can increase the complexity and risk of the product development. Longer Sprints can also reduce the agility and responsiveness of the Scrum Team to changing customer needs and market conditions. * The length of a Sprint should also be short enough to keep the business risk acceptable to the Product Owner. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time. The length of a Sprint affects how frequently and effectively the Product Owner can validate, verify, and deliver value to the customers and users. * The length of a Sprint should also be short enough to be able to synchronize the development work with other business events. The Scrum Team operates within a broader organizational context that may have other events, cycles, or deadlines that affect or depend on product development. For example, there may be marketing campaigns, sales promotions, regulatory compliance, or contractual obligations that require coordination and alignment with the product delivery. The length of a Sprint affects how well and timely the Scrum Team can synchronize their work with these other business events. References: * Scrum Guide: https://www.scrumguides.org/scrum-guide.html * Sprint: https://www.scrum.org/resources/what-is-a-sprint-in-scrum * Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
Question 152
What is the purpose of a Sprint Review? (choose the best answer)
Correct Answer: C
* The Sprint Review is an event that occurs at the end of each Sprint, where the Scrum Team and the stakeholders inspect the Increment and adapt the Product Backlog if needed. The Sprint Review is an opportunity for the Product Owner to validate that the Increment meets their expectations and delivers value to the customers and users. The Sprint Review is also an opportunity for the Developers to demonstrate their work and receive feedback from the Product Owner and the stakeholders. * The purpose of a Sprint Review is to inspect the product Increment with the stakeholders and collect feedback on next steps. The Sprint Review is a collaborative and interactive session where the Scrum Team and the stakeholders discuss what was done in the Sprint, what problems were encountered, what was learned, and what can be improved or changed. The Sprint Review also provides input for updating the Product Backlog to maximize value in future Sprints. * The other options are not valid or relevant purposes of a Sprint Review. They are either too vague, unrelated, or incorrect. They are: * To build team spirit: This is not a valid purpose of a Sprint Review. While team spirit is important for any Scrum Team, it is not the main focus or outcome of a Sprint Review. A Sprint Review is a formal event that has a specific agenda and goal, not a casual or social gathering. * To take time to judge the validity of the project: This is not a valid purpose of a Sprint Review. Scrum does not have a concept of a project, but rather a product. A product is a valuable solution that evolves over time to meet customer needs and market conditions. A project is a temporary endeavor with a fixed scope, time, and cost. A Sprint Review is not a time to judge or evaluate the validity of the product or its development, but rather to inspect and adapt it based on empirical evidence and feedback. * To review the Scrum Team's activities and processes during the Sprint: This is not a valid purpose of a Sprint Review. This is the purpose of another Scrum event called the Sprint Retrospective. The Sprint Retrospective is an event that occurs after the Sprint Review and prior to the next Sprint Planning, where the Scrum Team inspects how they worked during the Sprint and identifies improvements for the next Sprint. The Sprint Retrospective focuses on improving the Scrum Team's performance and process, not on inspecting the product Increment or its value. References: * Scrum Guide: https://www.scrumguides.org/scrum-guide.html * Sprint Review: https://www.scrum.org/resources/what-is-a-sprint-review
Question 153
Several Sprints into a project, the Product Owner tells the Scrum Master that a key stakeholder just started using the product. The stakeholder is unhappy with the quality of the product. What are two good options for the Scrum Master? (choose the best two answers)
Correct Answer: A,D
If a stakeholder is unhappy with the quality of the product, the Scrum Master can coach the Product Owner on how to effectively communicate this concern to the Developers1. The Scrum Master can also encourage the Product Owner to put quality specifications on the Product Backlog1. This allows the Developers to understand the stakeholder's expectations and work towards meeting them1. The Developers are responsible for building quality into the product, but the stakeholders (through the Product Owner) are responsible for setting what is expected in terms of product and process quality1.
Question 154
The Sprint is a formal opportunity to inspect and adapt Scrum artifacts.
Correct Answer: B
Question 155
A Sprint Retrospective should be held: (choose the best answer)
Correct Answer: C
Explanation The Sprint Retrospective is a time-boxed event for the Scrum Team to inspect how the last Sprint went and plan for improvements in the next Sprint. The Scrum Guide states that "The Sprint Retrospective concludes the Sprint. It is timeboxed to a maximum of three hours for a one-month Sprint. For shorter Sprints, the event is usually shorter."1 This means that the Sprint Retrospective should be held at the end of each Sprint, regardless of the project or release status. The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements, including to product quality and working relationships.1 References: 1: The Scrum Guide2, page 16 2: The Scrum Guide
