Scrum PSPO-I PDF Exam Questions:

The Product Owner is responsible for managing and refining the Product Backlog, which is the single source of truth for the plan of the product development. The Product Backlog is a living artifact that changes as the product and the market evolve. The Product Owner updates the Product Backlog continuously based on feedback, learning, and stakeholder needs. There is no separate project plan document in Scrum.

[Scrum Guide], section 3.1: ''The Product Backlog is an emergent, ordered list of what is needed to improve the product.''

[Professional Scrum Product Owner], chapter 5: ''The Product Backlog represents everything necessary to develop and launch a successful product.''

[What is a Product Backlog?]: ''The Product Backlog is a list of all things that need to be done within the project.''

Correct Answer: True

Dependencies are relationships between Product Backlog items that affect their order of implementation. For example, a Product Backlog item may depend on another one to be completed first, or it may have a dependency on a third-party system or resource. Dependencies could influence how the Product Owner orders Product Backlog items, as they may introduce risks, constraints, or uncertainties that affect the value delivery. The Product Owner should try to minimize dependencies and order the Product Backlog items in a way that maximizes value and minimizes waste.

[Professional Scrum Product Owner], chapter 6: ''Dependencies are relationships between Product Backlog items that affect their order of implementation.''

[Managing Dependencies on Agile Projects]: ''Dependencies can have a significant impact on the delivery of value.''

Correct Answers: A, C, and D.

The Sprint Retrospective is an event where the Scrum Team reflects on how they worked together in the last Sprint and identifies ways to improve their collaboration, processes, and quality. Therefore, appropriate topics for discussion in a Sprint Retrospective are:

Team relations: The Scrum Team should discuss how they communicated, interacted, and supported each other during the Sprint. They should celebrate their successes, acknowledge their challenges, and address any conflicts or issues that arose. They should also share feedback, appreciation, and suggestions for improvement with each other.

How the Scrum Team does its work: The Scrum Team should inspect the methods, tools, and practices they used to deliver the product increment. They should evaluate what worked well and what could be improved. They should also identify any impediments, risks, or dependencies that affected their work and how they handled them.

Definition of Done: The Scrum Team should review their Definition of Done and check if it is still relevant, clear, and achievable. They should also assess how well they adhered to it and if they delivered a potentially releasable product increment that meets the quality standards. They should also consider if they need to update or adapt their Definition of Done based on new insights or feedback.

The following topics are not appropriate for discussion in a Sprint Retrospective:

The value of work currently represented in the Product Backlog: The value of the Product Backlog items is the responsibility of the Product Owner, who should continuously refine and order them based on stakeholder needs and feedback. The value of the Product Backlog items is not directly related to how the Scrum Team works together and does not affect their improvement actions for the next Sprint.

Arranging the Sprint Backlog for the next Sprint: The Sprint Backlog is the plan for the next Sprint that is created by the Scrum Team during the Sprint Planning event. The Sprint Backlog is based on the Product Backlog items that are selected for the next Sprint and how the Developers intend to accomplish them. The Sprint Retrospective is not a planning event but a reflection event that focuses on the past Sprint.

[Scrum Guide], section 3.5: ''The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.''

[Professional Scrum Product Owner], chapter 7: ''The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.''

What is a Sprint Retrospective? | Scrum.org: ''During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of ''Done'' if appropriate and not in conflict with product or organizational standards.''

The Sprint Retrospective - What It Is & Tips for Making the Most of Your Meeting: ''The focus is on how the team worked together in the last sprint, including: Communication Teamwork Process Tools Systems Work environment Missing competencies Collaboration with external parties''

Correct Answer: A. Teach them that it is their responsibility to work with the

According to the Scrum Guide, the Scrum Team is responsible for all product-related activities, including coordination and integration with other teams. The Scrum Master should teach the Developers how to work with the other teams to create a potentially releasable product increment that meets the Definition of Done and the Product Goal. One way to facilitate this coordination is to use a Scrum of Scrums meeting, which is a daily or periodic meeting where representatives from each team share their progress, plans, and impediments. The Scrum of Scrums meeting is not mandatory, but it can help the teams align their work and resolve dependencies.

The other options are not correct because they violate the principles of Scrum, such as self-management, empiricism, and transparency:

B) Collecting the Sprint tasks from the teams and merging them into a consolidated plan for the entire Sprint is a centralized and controlled way of coordination that undermines the self-management and autonomy of the teams. The Scrum Master should not act as a project manager or a coordinator, but as a servant-leader and a coach who enables the teams to manage their own work.

C) Visiting the five teams each day to inspect that their Sprint Backlogs are aligned is a micromanagement and inspection approach that does not respect the trust and transparency of the teams. The Scrum Master should not interfere with the work of the teams, but support them in creating a shared understanding of the product vision, goals, and requirements.

D) Teaching the Product Owner to work with the lead developers on ordering Product Backlog in a way to avoid too much overlap during a Sprint is a suboptimal and inefficient way of coordination that does not leverage the collective intelligence and creativity of the teams. The Product Owner should not rely on a few individuals to order the Product Backlog, but collaborate with all the teams and stakeholders to maximize value delivery.

[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.''

Scrum Of Scrums - Guide to Agile Scaling Frameworks - Agilest: ''The coordination of the various teams is done in a Scrum of Scrums meeting which can be held daily, twice a week, or at a minimum, once a week. Each Scrum team has its ScrumMaster or a designated team member attend the Scrum of Scrum meeting as its representative.''

Correct Answer: D. Never. The entire Scrum Team is accountable for creating

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.

[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''