PSPO-I Exam Dumps - Scrum PSPO Questions and Answers

The Developers are the people in the Scrum Team who are committed to creating any aspect of a usable Increment each Sprint. The Developers are accountable for organizing and managing their work.Only the Developers can decide how to perform the work during the Sprint1. The Developers plan the work necessary to create an Increment that meets the Definition of Done during the Sprint Planning event. This is often done by decomposing Product Backlog items into smaller work items of one day or less.How this is done is at the sole discretion of the Developers2.The Developers also inspect their progress toward the Sprint Goal and adapt their plan during the Daily Scrum1.The Developers are self-managing, which means they decide internally who does what, when, and how1. The Scrum Master, the Product Owner, the team manager, and the subject matter experts are not involved in determining how the work is performed during the Sprint.They may provide guidance, feedback, or support, but they do not interfere with the Developers’ autonomy and accountability134.References:

Scrum Guide

What is a Developer?

Who Determines How Work Is Performed During The Sprint?

What is Sprint Planning?

 It is not true that the Product Owner must write all of the Product Backlog items (e.g. user stories, requirements, etc.) on the Product Backlog before handing them over to the Scrum Team. This is because:

The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is never complete and constantly changes to reflect the needs and desires of the customers, users, and stakeholders.

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for identifying and articulating the Product Goal, which is a long-term objective for the product that guides all the activities of the Scrum Team.

The Product Owner is also accountable for managing the Product Backlog items effectively. They must ensure that they are transparent, visible, and understood by everyone who needs to work on them. They must also collaborate with the Developers and stakeholders to refine, order, and prioritize them based on value and impact.

The Product Owner does not need to write all of the Product Backlog items by themselves or before handing them over to the Scrum Team. They can involve others in creating or contributing to them, such as customers, users, stakeholders, or Developers. They can also add or modify them at any time during the product development process, as long as they are clear and ready for selection in Sprint Planning.

The correct answer isB.

Scrum does not require the Product Owner to use any specific technique or reporting tool. The Scrum Guide defines accountabilities, events, artifacts, and commitments, but it does not prescribe tools such as burn-up charts, burndown charts, or Critical Path Analysis.

The Product Owner is accountable for maximizing value and for effective Product Backlog management, but how this is done can vary depending on the context. Techniques like burn-up charts or burndown charts may be useful, but they are optional and not mandatory in Scrum.

Why the other options are incorrect:

A. Feature burn-up— may be useful, but Scrum does not require it.

C. Critical Path Analysis— belongs more to traditional project management and is not a Scrum requirement.

D. Burndown chart— commonly used by some teams, but not required by Scrum.

 These are the best answers because they ensure that security concerns are addressed in a transparent and consistent way. By adding security criteria to the Definition of Done, the Scrum Team can make sure that every Increment meets a high standard of quality and security. By creating Product Backlog items for specific security concerns, the Scrum Team can prioritize and plan them in collaboration with the Product Owner and stakeholders. References:

Scrum Guide, page 14: “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, page 15: “The Product Backlog is an emergent, ordered list of what is needed to improve the product.”

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

The Scrum Team is a self-managing unit that organizes its own work and delivers a valuable product1. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers2. The Scrum Team is accountable for creating a valuable, useful Increment every Sprint[3][3] . If a Developer is having conflicts with other team members that affect the delivery of the Increment, the Scrum Team is responsible for resolving the issue and deciding whether to remove the Developer from the team or not. The Product Owner, the Scrum Master, and the hiring manager do not have the authority to remove a Developer from the Scrum Team, as this would violate the principle of self-management4.

The Definition of Done is a shared understanding of what it means for work to be complete, and ensures transparency of the quality of the work done1. A Product Backlog item is considered complete when it meets the Definition of Done, which means that it is usable and potentially releasable, and that it meets the quality standards set by the Scrum Team and the stakeholders2. The other options are not sufficient to determine the completeness of a Product Backlog item, as they may not reflect the actual value and quality of the product.

 The timebox for the Sprint Review is four hours for a one-month Sprint. This is because:

The Sprint Review is an event where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog if needed. The purpose of the Sprint Review is to elicit feedback and foster collaboration.

The timebox for each Scrum event is proportional to its frequency and duration. A one-month Sprint corresponds to a maximum calendar month.

The timebox for a one-month Sprint Review is four hours. For shorter Sprints, it is usually shorter.

The timebox ensures that there is enough time to inspect what has been done in relation to what could be done next and make any necessary adaptations to optimize value.

Other options, such as two hours for a one-month Sprint, one day, or as long as needed, are not valid answers as they do not reflect the correct timebox for the Sprint Review.

 The best way to minimize dependencies between the Scrum Teams is to work with the Developers on how to best analyze and break apart the work. This is because:

The Developers are accountable for creating a “Done” Increment in every Sprint. They must ensure that every Product Backlog item they work on meets the Definition of Done before it is considered complete.

The Developers are self-managing professionals who organize and manage their own work. They decide how to best accomplish their work, rather than being directed by others outside the Scrum Team.

The Developers are cross-functional, meaning they have all the skills and competencies needed to accomplish the work without depending on others who are not part of the team.

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for identifying and articulating the Product Goal, which is a long-term objective for the product that guides all the activities of the Scrum Team.

The Product Owner is the sole person responsible for managing the Product Backlog, which is an emergent, ordered list of what is needed to improve the product. They must ensure that the Product Backlog is transparent, visible, and understood by everyone who needs to work on it.

The Product Owner and the Developers must collaborate closely throughout the Sprint to ensure that they have a shared understanding of what they are building and why. The Product Owner must provide clarifications, feedback, and guidance to the Developers as needed to help them create a valuable Increment.

When there are multiple teams working on one product, it is important to minimize dependencies between them to avoid delays, conflicts, or waste. Dependencies may arise due to technical, functional, or organizational factors that affect how the teams can deliver value independently and effectively.

To minimize dependencies, the Product Owner should work with the Developers on how to best analyze and break apart the work into smaller and more manageable pieces that can be delivered by each team without relying on others. This may involve applying techniques such as feature slicing, component splitting, or domain-driven design. The Product Owner should also communicate and coordinate with other Product Owners and stakeholders to align expectations and priorities across teams.

Other options, such as creating an independent Product Backlog per Scrum Team, dividing Product Backlog items among six Product Owners, identifying the dependencies and re-ordering the Product Backlog for the other five Product Owners, or raising this as an impediment with the Scrum Master, are not valid answers as they do not reflect how to minimize dependencies between the Scrum Teams or how to apply the Scrum values and principles.