Correct Answer: CDE

The advantages of a Product Owner sharing a clearly defined Product Goal with the Scrum Team are:

It provides a good overall direction so Sprints will feel less like isolated pieces of work. The Product Goal is a long-term objective for the product that guides all the activities of the Scrum Team. It helps the Scrum Team align their efforts and

focus on delivering value that contributes to the product vision. It helps the Scrum Team keep focus and they can weigh any decision against the Product Goal. The Product Goal serves as a filter for deciding what to work on and what not to

work on. It helps the Scrum Team prioritize and optimize their work based on value and impact.

It is easier to inspect incremental progress at the Sprint Review. The Sprint Review is an event where the Scrum Team and the stakeholders collaborate on the product and inspect how it meets the Product Goal. The Increment is a concrete

and usable outcome of the Sprint that provides a measure of progress towards the Product Goal.

Other options, such as helping the Developers estimate the date that the Product Backlog will be complete or being not mandatory in Scrum, are not valid advantages of having a Product Goal. They may reflect a misunderstanding of what a

Product Goal is or how Scrum works.

References:

[Scrum Guide], page 10, section "Product Goal"

[Professional Scrum Product OwnerTM Training], page 6, section "Product Vision" [Professional Scrum Product OwnerTM Training], page 7, section "Product Backlog Management"

[Scrum Guide], page 13, section "Sprint Review"

[Scrum Guide], page 10, section "Increment"

Correct Answer: A

Correct Answer: A

According to Scrum.org, when splitting a large group into multiple Scrum Teams, it can be beneficial to allow the people to self-organize into smaller teams12. This approach respects the principle of self-organization, which is a key aspect of Scrum12. It allows individuals to choose the team they feel they can contribute to most effectively12. However, it's important to note that this process should be facilitated and guided to ensure a balanced distribution of skills and capabilities across the teams12.

Correct Answer: AC

Non-functional requirements are the criteria that define the quality, performance, security, usability, and other aspects of a product1. They are often implicit or assumed, but they are important to make visible and explicit, as they affect the value and satisfaction of the product2. One effective way to make non-functional requirements visible is to add them to the Product Backlog, which is an ordered list of everything that is known to be needed in the product[3][3]. By adding nonfunctional requirements to the Product Backlog, the Product Owner and the Developers can prioritize, refine, and estimate them, and make them transparent to the stakeholders4. Another effective way to make non-functional requirements visible is to add them to the Definition of Done, which is a shared understanding of what it means for work to be complete, and ensures transparency of the quality of the work done5. By adding non-functional requirements to the Definition of Done, the Developers can ensure that every Product Backlog item and Increment meets the expected quality standards, and that the work is taken care of every Sprint. References:

1: Non-functional requirement, Wikipedia, accessed on December 16, 2023

2: Managing Products with Agility, Scrum.org, accessed on December 16, 2023 [3][3]: The Scrum Guide, November 2020, p. 6

4: The Scrum Guide, November 2020, p. 7

5: The Scrum Guide, November 2020, p. 13 Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023

Correct Answer: C

The best approach for Scrum Teams to produce valuable Increments is to be accountable for developing functionality from beginning to end, as this enables them to deliver potentially releasable products that meet the definition of "Done".

The Scrum Guide states that "The Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint."1 This means that the Developers are not limited by the boundaries of

components, layers, or technologies, but rather they collaborate and coordinate to deliver a complete and integrated product that satisfies the Sprint Goal and the Product Owner's expectations.

References:

1: The Scrum Guide2, page 7

2: The Scrum Guide

Correct Answer: D

Correct Answer: C

Explanation: The Developers on the Scrum Team share accountability for the Sprint Backlog, which is a forecast of the work and the plan to deliver the Sprint Goal12. The Sprint Backlog is dynamic and can be updated by the Developers as more is learned during the Sprint34. The Developers are not individually accountable for the items in the Sprint Backlog, nor are they assigned by the Scrum Master or the Product Owner5.

Correct Answer: A

Explanation: The Scrum Guide states that "By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint. Implementing these improvements in the next Sprint is the adaptation to the inspection of the Scrum Team itself."1 This means that the Scrum Team may add the high priority process improvements to the Sprint Backlog for the next Sprint, as part of their plan to deliver the Increment and achieve the Sprint Goal. The Sprint Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned.1 References:

1: The Scrum Guide2, page 16

2: The Scrum Guide

Correct Answer: C

The best statement that describes Scrum is: A framework to generate value through adaptive solutions for complex problems. Scrum is a lightweight framework that helps people, teams, and organizations to deliver valuable products in complex and uncertain environments. Scrum is based on empiricism, which means that knowledge comes from experience and making decisions based on what is observed. Scrum employs an iterative and incremental approach to optimize predictability and control risk. Scrum is not a defined and predictive process, a complete methodology, or a cookbook that defines best practices. Scrum provides the minimal boundaries within which teams can self-organize and create innovative solutions. References: Scrum Guide, Section 1 (Definition of Scrum) and Section 2 (Uses of Scrum)

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. References: The Scrum Guide Understanding and Applying the Scrum Framework Professional Scrum Product OwnerTM I Certification