Scrum PSPO-I Practice Test - Questions Answers, Page 16

The Scrum Guide defines a Scrum Team as "a cohesive unit of professionals focused on one objective at a time, the Product Goal". It also states that "the Scrum Team consists of one Scrum Master, one Product Owner, and Developers". Therefore, the correct answer is A, B, and D. Customers and users are not part of the Scrum Team, but they are important stakeholders who provide feedback and input to the Product Owner and the Developers.

The Scrum Guide, section 2.1. The Scrum Team

Professional Scrum Product Owner I (PSPO I) Learning Path, section 1.1. The Scrum Team

Professional Scrum Product Owner I (PSPO I) Sample Questions, question 1

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". It also states that "the Developers can do the work of any other role on the Scrum Team, as long as accountability is met". Therefore, the Developers on the Scrum Team should write the user documentation, as it is part of the Definition of Done and the work needed to deliver a "Done" Increment. The other options are not acceptable, as they violate the Scrum values of commitment, focus, and respect, and they create dependencies, delays, and waste.

The Scrum Guide, section 2.2. Developers

Professional Scrum Product Owner I (PSPO I) Learning Path, section 2.3. The Product Owner and the Definition of Done

Professional Scrum Product Owner I (PSPO I) Sample Questions, question 12

The Scrum Guide states that "Sprints are the heart of Scrum where ideas are turned into value". It also states that "Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint". Furthermore, it states that "Sprints are limited to one calendar month. When a Sprint's horizon is too long the definition of what is being built may change, complexity may rise, and risk may increase". Therefore, the correct answer is B. The other options are not acceptable, as they contradict the Scrum principles of empiricism, self-organization, and adaptation.

The Scrum Guide, section 3.1. Sprints

Professional Scrum Product Owner I (PSPO I) Learning Path, section 2.2. The Product Owner and the Sprint

A Scrum Master does not fulfill the same role as a traditional Project Manager.A Project Manager is typically responsible for planning, executing, monitoring, controlling, and closing a project, as well as managing the scope, schedule, budget, quality, risks, and stakeholders of the project1.A Scrum Master is a servant-leader for the Scrum Team, who helps the team understand and enact Scrum values, principles, and practices, and removes impediments to the team's progress2. A Scrum Master does not manage the project, the scope, the schedule, the budget, or the team, as these are either shared responsibilities or emergent outcomes of the Scrum framework[3][3].A Scrum Master also does not have authority over the team or the stakeholders, but rather facilitates collaboration and empowerment among them4.

1:What is Project Management?, Project Management Institute, accessed on December 16, 2023

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

[3][3]:Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023

4:Developing People and Teams, Scrum.org, accessed on December 16, 2023

Multiple Scrum Teams working on the same product do not have to have the same Sprint start date.The Scrum Guide does not prescribe any synchronization of Sprints across multiple teams1.However, it is recommended that the teams align their Sprint cadence and duration, and coordinate their dependencies and integration through a shared Product Backlog, a common Definition of Done, and frequent communication2. This way, the teams can deliver a coherent and valuable product Increment every Sprint[3][3].

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

2:Managing Products with Agility, Scrum.org, accessed on December 16, 2023

[3][3]:Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023

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 non-functional 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.

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

The Developers are the ones who determine how many Product Backlog items they select for a Sprint.The Developers are self-managing and decide how much work they can do in a Sprint1.The Product Owner and the Developers collaborate on the scope of the Sprint during Sprint Planning, but the final decision is up to the Developers2. The Product Owner, the Scrum Master, and the stakeholders do not have the authority to tell the Developers how many Product Backlog items they should select, as this would violate the principle of self-management[3][3].

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

2:The Scrum Guide, November 2020, p. 10

[3][3]:Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023