Correct Answer: D

Explanation: The Sprint Backlog is the output of the Sprint Planning, where the Developers select the Product Backlog items that they can deliver in the Sprint and create a plan for how to do the work. The Scrum Guide states that "The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how)."1 The Sprint Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned. The Sprint Backlog makes visible all the work that the Developers identify as necessary to meet the Sprint Goal.1 References:

1: The Scrum Guide2, page 15

2: The Scrum Guide

Correct Answer: A

The Scrum Master should allow the Developers to self-manage and determine for themselves what to do because:

It respects the autonomy and empowerment of the Developers. The Developers are accountable for organizing and managing their own work, and they are the best people to decide how to conduct their Daily Scrum. The Scrum Master

should not impose or dictate how the meeting should be set up or run, as that would undermine the self-organization and collaboration of the Developers. It supports the continuous improvement and adaptation of the Developers. The

Developers are expected to inspect and adapt their process and practices, and to find ways to overcome any challenges or impediments they face. The Scrum Master should not solve the problems for them, but rather facilitate their problem-

solving and learning abilities.

It aligns with the role and responsibilities of the Scrum Master. The Scrum Master is responsible for promoting and supporting Scrum, and for helping everyone understand and enact Scrum theory, values, principles, and practices. The Scrum

Master is not a manager or a leader of the Developers, but rather a servant-leader who enables them to work effectively.

References:

Scrum Guide 2020, page 6: "Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint." Scrum Guide 2020, page 6: "The Developers are accountable for ... organizing and

managing their work."

Scrum Guide 2020, page 12: "The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work. This

creates focus and improves self-management."

Scrum Guide 2020, page 13: "The Daily Scrum is an internal meeting for the Developers. If others are present, the Scrum Master ensures that they do not disrupt the meeting."

Scrum Guide 2020, page 7: "The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the

organization."

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

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: 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

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: B

Correct Answer: A

The Developers are the ones who are accountable for tracking the remaining work toward the Sprint Goal. The Developers are self-managing and decide how much work they can do in a Sprint1. They also create and update the Sprint Backlog, which is the plan for how the Developers will achieve the Sprint Goal, and the single source of truth for the work to be done in the Sprint2. The Developers use the Daily Scrum to inspect their progress toward the Sprint Goal and adapt the Sprint Backlog as necessary[3][3]. The Product Owner, the Scrum Master, and the Project Manager (if any) do not have the accountability for tracking the remaining work toward the Sprint Goal, as this is the responsibility of the Developers. References:

1: The Scrum Guide, November 2020, p. 6

2: The Scrum Guide, November 2020, p. 10 [3][3]: The Scrum Guide, November 2020, p. 11

Correct Answer: B

A Product Owner is not the same thing as a traditional Project Manager. A Product Owner is a role in Scrum, a framework for developing, delivering, and sustaining complex products. A Project Manager is a role in traditional project

management, a discipline for planning, executing, and controlling projects. A 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.

A Project Manager is accountable for delivering the project within the predefined scope, time, and cost constraints. The Project Manager is responsible for defining and managing the project plan, resources, risks, issues, and dependencies.

The Project Manager coordinates and controls the activities of the project team and the stakeholders and ensures that the project meets the quality standards and expectations.

Some of the main differences between a Product Owner and a Project Manager are:

References:

Scrum Guide: https://www.scrumguides.org/scrum-guide.html Product Owner: https://www.scrum.org/resources/what-is-a-product-owner Project Manager: https://www.pmi.org/about/learn-about-pmi/what-is-project- management

Correct Answer: C

A sprint review is a collaborative event where the Scrum Team and stakeholders inspect the outcome of a Sprint and determine future adaptations12. It is not a mechanism to control, reward, or punish the Developers, nor is it just a demo of the work done.

Correct Answer: D

The Sprint Backlog is created during Sprint Planning, where the Developers select the Product Backlog items that they can deliver in the Sprint and create a plan for how to do the work. The Scrum Guide states that "The Sprint Backlog is

composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how)."1 The Sprint Backlog is owned and managed by the Developers, who can

update it throughout the Sprint as more is learned.

References:

1: The Scrum Guide2, page 15

2: The Scrum Guide