Cisco®
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
Microsoft
VMware
Avaya
SAP
Google
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
All Vendors
  2. Home
  3. Exams
  4. Scrum
  5. PSPO-I

Free Scrum PSPO-I Exam Braindumps (page: 3)

96.4% Passing Rate DOWNLOAD PDF EXAM
178 Questions & Answers
Page 3 of 43

When does a Developer become accountable for the value of a Product Backlog item selected for the Sprint?
(choose the best answer)

  1. Whenever a team member can accommodate more work.
  2. At the Sprint Planning Event.
  3. During the Daily Scrum.
  4. Never. The entire Scrum Team is accountable for creating value every Sprint.

Answer(s): D

Explanation:

Answer(s): D) Never. The entire Scrum Team is accountable for creating value every Sprint.
According to the Scrum Guide, the Scrum Team consists of one Product Owner, one Scrum Master, and Developers. The Scrum Team is responsible for all product-related activities, including delivering a valuable, usable product increment every Sprint. The Product Owner is accountable for maximizing the value of the product and the work of the Developers. The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog; instilling quality by adhering to a Definition of

Done; and adapting their plan each day toward the Sprint Goal. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, helping everyone understand Scrum theory and practice, and removing impediments to the Scrum Team's progress. Therefore, the Developers are not individually accountable for the value of a Product Backlog item selected for the Sprint, but collectively accountable as part of the Scrum Team. The value of a Product Backlog item is determined by the Product Owner, who orders the Product Backlog items based on stakeholder needs and feedback. The Developers collaborate with the Product Owner to understand the value and requirements of each Product Backlog item and deliver a potentially releasable product increment that meets the Definition of Done and the Sprint Goal.


Reference:

[Scrum Guide], section 2.2: "The Scrum Team is responsible for all product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else that might be required." Accountabilities in Scrum | Scrum.org: "Scrum has three accountabilities, each with a different focus :
Product Owner (green figure) The "What". With a focus on Value, time to market, return on investment and Total Cost of Ownership (TCO). Developers (red figures) The "How". Focus on building something that is Done ­ that the increment is useable and potentially releasable." What is a Developer in Scrum? | Scrum.org: "The specific skills needed by the Developers are often broad and will vary based on the type of work they are doing. However, the Developers are always accountable for: Creating a plan for the Sprint, the Sprint Backlog Instilling quality by adhering to a Definition of Done Adapting their plan each day toward the Sprint Goal"



True or False: Product Owners must specify complete acceptance criteria for a Product Backlog item before the Developers can select the item in Sprint Planning.

  1. True
  2. False

Answer(s): B

Explanation:

False: Product Owners do not have to specify complete acceptance criteria for a Product Backlog item before the Developers can select the item in Sprint Planning. Acceptance criteria are a set of conditions that a Product Backlog item must satisfy to be considered

"Done" and acceptable for delivery.
Acceptance criteria are not mandatory in Scrum, but they can help the Product Owner and the Developers to clarify the expectations and requirements of a Product Backlog item. Acceptance criteria can be added or refined by the Product Owner at any time, but they should be clear and testable before the Sprint starts.
The Developers can select a Product Backlog item in Sprint Planning based on their understanding of its value, scope, and complexity, as well as their capacity and skills. They can also collaborate with the Product Owner to define or refine the acceptance criteria during Sprint Planning.


Reference:

Scrum Guide, Section 3.4 (The Product Backlog), Section 5.1 (Sprint Planning), and Section 6.4 (The Increment)



Why would you expect a Product Owner to care that the Scrum Team adheres to its Definition of Done?
(choose the best two answers)

  1. The Product Owner should not concern themselves with meeting the Definition of Done, it is the Developer's responsibility.
  2. To be able to punish the team when they do not meet their velocity goal for the Sprint.
  3. To forecast the team's productivity over time.
  4. The Definition of Done can affect the product's total cost of ownership.
  5. To have complete transparency into what has been done at the end of each Sprint.

Answer(s): C,D

Explanation:

The Product Owner should care that the Scrum Team adheres to its Definition of Done because:
It helps to forecast the team's productivity over time. By having a clear and consistent Definition of Done, the Product Owner can measure the amount of work that the team can deliver in each Sprint and plan accordingly.
It affects the product's total cost of ownership. By ensuring that the work done by the team meets the quality standards and expectations of the stakeholders, the Product Owner can reduce the risk of technical debt, rework, defects, and maintenance costs in the future.


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 11: "The Product Owner is accountable for effective Product Backlog management, which includes ... ordering Product Backlog items; and, ensuring that the Product Backlog is transparent, visible and understood."
Scrum Guide 2020, page 14: "The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog for future consideration."



How is management that is external to the Scrum Team involved in the Daily Scrum? (choose the best answer)

  1. The Product Owner represents their opinions.
  2. The Scrum Master speaks on their behalf.
  3. Managers are not required at the Daily Scrum.
  4. Management gives an update at the start of each Daily Scrum.

Answer(s): C

Explanation:

Management that is external to the Scrum Team is not involved in the Daily Scrum because:
The Daily Scrum is an event for the Developers to inspect their progress towards the Sprint Goal and adapt their Sprint Backlog accordingly. It is not a status meeting or a reporting session for managers or other stakeholders.
The presence of external managers may hinder the self-organization, collaboration, and transparency of the Developers. It may also create pressure, interference, or distraction for the team. The Scrum Master is responsible for ensuring that the Daily Scrum is held and that only the Developers participate. The Product Owner and other stakeholders may attend as observers, but only if the Developers find it useful.


Reference:

Scrum Guide 2020, page 12: "The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work." Scrum Guide 2020, page 13: "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."






Post your Comments and Discuss Scrum PSPO-I exam prep with other Community members:

PSPO-I Exam Discussions & Posts