Tested Material Used To PSPO-I Test Engine Exam Questions in here [Dec-2025]
Penetration testers simulate PSPO-I exam PDF
Scrum PSPO-I or Professional Scrum Product Owner I exam is a globally recognized certification for Product Owners in the Scrum framework. It is designed to test and validate the knowledge and skills of Product Owners in managing products and maximizing the value of the product.
Scrum PSPO-I exam is a valuable opportunity for individuals who want to become certified product owners and demonstrate their expertise in Scrum. By passing the exam, individuals can enhance their career prospects, gain recognition for their skills and knowledge, and contribute to the success of organizations that use Scrum as their preferred agile framework.
Scrum PSPO-I Certification Exam is an online, time-boxed exam that consists of 80 multiple-choice questions. PSPO-I exam duration is 60 minutes, and candidates must score at least 85% to pass. PSPO-I exam covers a wide range of product ownership topics, including product vision, product backlog management, stakeholder management, and product value optimization. PSPO-I exam questions are designed to test the candidate's knowledge of Scrum theory and their ability to apply Scrum practices to real-world situations.
NEW QUESTION # 33
Which two ways of creating Scrum Teams are consistent with Scrum's values?
(choose the best two answers)
- A. Managers collaborate to assign individuals to specific teams.
- B. Existing teams propose how they would like to go about organizing into the new structure.
- C. Managers personally re-assign current subordinates to new teams.
- D. The Chief Product Owner determines the new team structures and assignments.
- E. Bring all the people together and let them organize into Scrum Teams.
Answer: B,E
Explanation:
Explanation
The Scrum values are commitment, focus, openness, respect, and courage1. These values are embodied by the Scrum Team, which is a self-managing unit that organizes its own work and delivers a valuable product2. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers[3][3]. The best way to create Scrum Teams is to respect the self-management and empowerment of the people who will do the work, and let them decide how to organize themselves into Scrum Teams. This can be done by bringing all the people together and letting them form Scrum Teams based on their skills, interests, and alignment with the product vision4. Alternatively, existing teams can propose how they would like to reorganize themselves into Scrum Teams, based on their feedback and experience5. These ways of creating Scrum Teams are consistent with the Scrum values, as they foster commitment, focus, openness, respect, and courage among the team members and stakeholders. The other options are not consistent with the Scrum values, as they involve managers or the Chief Product Owner imposing their decisions on the team members, which undermines their self-management and empowerment, and creates a lack of trust and collaboration.
References:
1: The Scrum Guide, November 2020, p. 4
2: The Scrum Guide, November 2020, p. 5
[3][3]: The Scrum Guide, November 2020, p. 6
4: Managing Products with Agility, Scrum.org, accessed on December 16, 2023
5: Developing People and Teams, Scrum.org, accessed on December 16, 2023
NEW QUESTION # 34
Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint.
- A. TRUE
- B. FALSE
Answer: A
NEW QUESTION # 35
Who has the final decision about the order of items in the Product Backlog?
(choose the best answer)
- A. The Product Owner.
- B. The Scrum Master.
- C. The Developers.
- D. The Stakeholders.
- E. The Scrum Team.
Answer: C
Explanation:
In Scrum, the Product Owner is responsible for maximizing the value of the product resulting from the work of the Development Team. One of the primary ways the Product Owner does this is by managing the Product Backlog, which includes clearly expressing Product Backlog items, ordering the items to best achieve goals and missions, and ensuring that the Product Backlog is visible, transparent, and clear to all. This means that the Product Owner has the final authority on the order of items in the Product Backlog, as they are best positioned to understand the strategic and market value of the work to be done.
References: The Scrum Guide and the Professional Scrum Product Owner™ (PSPO I) study materials, specifically the sections on 'Managing Products with Agility' and 'Understanding and Applying the Scrum Framework', which outline the accountabilities of the Product Owner in managing the Product Backlog
NEW QUESTION # 36
The Developers find out during the Sprint that they are not likely to build everything they forecast. What would you expect a Product Owner to do?
(choose the best answer)
- A. Re-work the selected Product Backlog items with the Developers to meet the Sprint Goal.
- B. Cancel the Sprint.
- C. Inform management that more Developers are needed.
- D. Skip Product Backlog refinement activities.
- E. Change the Sprint Goal.
Answer: A
Explanation:
Explanation
If the Developers find out during the Sprint that they are not likely to build everything they forecast, the best response from the Product Owner is to re-work the selected Product Backlog items with the Developers to meet the Sprint Goal. This is because:
* The Sprint Goal is a short-term objective that provides guidance and focus to the Scrum Team throughout the Sprint. It is a flexible and negotiable commitment that can be adjusted as more is learned throughout the Sprint.
* 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 Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They must inspect the Increment at the end of each Sprint and assess how it delivers value and contributes to the Product Goal.
* 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.
* If the Developers find out during the Sprint that they are not likely to build everything they forecast, it means that there is a gap between their initial plan and their actual progress. This may happen due to various reasons, such as new insights, changing requirements, technical challenges, or unforeseen circumstances.
* In this situation, the Product Owner should work with the Developers to re-work the selected Product Backlog items to meet the Sprint Goal. This may involve adding, removing, or modifying some items, as long as they still support the Sprint Goal and deliver value. The Product Owner should also communicate any changes or impacts to the stakeholders and customers as appropriate.
Other options, such as skipping Product Backlog refinement activities, informing management that more Developers are needed, changing the Sprint Goal, or canceling the Sprint, are not valid responses from the Product Owner as they do not reflect what should happen in Scrum or how to deal with uncertainty and complexity.
References:
* [Scrum Guide], page 15, section "Sprint Goal"
* [Scrum Guide], page 7, section "Developers"
* [Scrum Guide], page 6, section "Product Owner"
* [Scrum Guide], page 10, section "Definition of Done"
* [Scrum Guide], page 10, section "Increment"
* [Scrum Guide], page 10, section "Product Goal"
NEW QUESTION # 37
Who is on the Scrum Team?
(choose all that apply)
- A. Project Manager.
- B. Scrum Master.
- C. None of the above.
- D. Developers.
- E. Product Owner.
Answer: B,D,E
Explanation:
Explanation
The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal. 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. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for creating and communicating a vision, ordering the Product Backlog, and ensuring that the best possible job is done to delight customers. The Developers are the people in the Scrum Team that are committed to delivering a "Done" Increment that meets the Definition of Done and the Sprint Goal. They are responsible for managing and organizing their work within the Sprint, collaborating with the Product Owner and the Scrum Master, and applying their skills and creativity to create a product that delivers value to the stakeholders and customers. A Project Manager is not a role in the Scrum Team, as Scrum does not recognize titles for Developers, regardless of the work being performed by the person. There is no need for a Project Manager, as the Scrum Team is self-managing and accountable for delivering value.
References:
* The Scrum Guide
* The Scrum Team
* Professional Scrum Product Owner™ I Certification
NEW QUESTION # 38
The Product Owner ist allowed to participate in the Daily Scrum if:
- A. They the Product Owner is actively working on items in the Sprint Backlog.
- B. It is allowed by the Developers.
- C. It is allowed by the Scrum Master.
Answer: A
NEW QUESTION # 39
Scrum is based on empiricism. All of its artifacts must be transparent to ensure sufficient accuracy of inspection. How can the Scrum Team maintain the Product Backlog to maximize its transparency?
(choose the best answer)
- A. Product Backlog items must be sized such that the highest ordered items are no bigger than a Sprint.
- B. Product Backlog items should hold no more than 8 points of work, which is the average in the range of acceptable sizes of 1, 2, 3, 5, 8, and 13.
- C. The Product Backlog is only updated at a release planning meeting with the stakeholders and the change control board present.
- D. The Product Backlog is continually kept up to date with the most recent insights.
- E. The Product Backlog is only updated at the Sprint Review, when both the Scrum Team and the stakeholders are available.
Answer: D
Explanation:
The Scrum Team can maintain the Product Backlog to maximize its transparency by continually keeping it up to date with the most recent insights because:
It reflects the current state of the product and the work. The Product Backlog is a dynamic and emergent artifact that represents all the possible features, functions, requirements, enhancements, and fixes that constitute changes to the product. By updating it frequently, the Scrum Team can ensure that the Product Backlog is accurate, complete, and relevant.
It enables the Product Owner to optimize the value of the product and the work of the Scrum Team. The Product Owner is accountable for effective Product Backlog management, which includes ordering, refining, and communicating the Product Backlog items. By updating it frequently, the Product Owner can incorporate new learnings, feedback, opportunities, and changes into the product decisions and priorities.
It supports the inspection and adaptation of the Scrum Team and the stakeholders. The Product Backlog is a source of information and transparency for everyone involved in the product development. By updating it frequently, the Scrum Team and the stakeholders can inspect the progress and outcomes of each Sprint, and adapt their plans and actions accordingly.
Reference:
Scrum Guide 2020, page 10: "The Product Backlog is an emergent, ordered list of what is needed to improve the product." Scrum Guide 2020, page 11: "The Product Owner is accountable for effective Product Backlog management, which includes ... ensuring that the Product Backlog is transparent, visible and understood." Scrum Guide 2020, page 11: "The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions." Scrum Guide 2020, page 11: "Higher ordered Product Backlog items are clearer and more refined than lower ordered ones." Scrum Guide 2020, page 15: "The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration."
NEW QUESTION # 40
Your management has asked you to take the lead in the development of a new product. Six teams new to Scrum will build this product.
You have gathered a number of requirements and ideas into an early form of a Product Backlog. How would you minimize dependencies between the Scrum Teams?
(choose the best answer)
- A. You divide Product Backlog items among the six Product Owners.
- B. You work with the Developers on how to best analyze and break apart the work.
- C. You create an independent Product Backlog per Scrum Team.
- D. You raise this as an impediment with the Scrum Master.
- E. You identify the dependencies and re-order the Product Backlog for the other five Product Owners.
Answer: B
Explanation:
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.
Reference:
[Scrum Guide], page 7, section "Developers"
[Scrum Guide], page 6, section "Product Owner"
[Scrum Guide], page 10, section "Definition of Done"
[Scrum Guide], page 10, section "Increment"
[Scrum Guide], page 10, section "Product Goal"
[Scrum Guide], page 11, section "Product Backlog"
[Professional Scrum Product Owner Training], page 9, section "Business Strategy"
[Professional Scrum Product Owner Training], page 8, section "Release Management"
NEW QUESTION # 41
Which statement best describes a Product Owner's responsibility?
(choose the best answer)
- A. Keep stakeholders from distracting the Developers.
- B. Ensuring that the work meets the commitments to the stakeholders.
- C. Maximizing the value of the work the Scrum Team does.
- D. Directing the Developers.
Answer: C
Explanation:
Explanation
The 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 creating and communicating a vision, ordering the Product Backlog, and ensuring that the best possible job is done to delight customers. The Product Owner does not manage the Developers, but collaborates with them and the Scrum Master to optimize the value delivery. The Product Owner does not ensure that the work meets the commitments to the stakeholders, but rather that the work delivers value to the stakeholders. The Product Owner does not keep stakeholders from distracting the Developers, but rather engages them and manages their expectations.
References:
* Professional Scrum Product Owner™ I Certification
* [The Scrum Guide]
* [The Product Owner]
NEW QUESTION # 42
How often should Scrum Team membership change?
(choose the best answer)
- A. Every Sprint to promote shared learning.
- B. As needed, while taking into account a short-term reduction in productivity.
- C. As needed, with no special allowance for changes in productivity.
- D. Never, it reduces productivity.
Answer: B
Explanation:
The Scrum Team membership should change as needed, but not too frequently, as it may affect the team's ability to deliver value and maintain a high level of collaboration and self-organization. The Scrum Guide states that "Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint. Fewer than three Development Team members decrease interaction and results in smaller productivity gains. Having more than nine members requires too much coordination. Large Development Teams generate too much complexity for an empirical process to be useful."1 Therefore, the Scrum Team should consider the impact of changing its membership on its productivity and performance, and balance the need for stability and flexibility.
Reference:
1: The Scrum Guide2, page 6
2: The Scrum Guide
NEW QUESTION # 43
Developers are self-managing, which of the following do they manage?
(choose the best answer)
- A. Sprint Backlog.
- B. When to release, based on its progress.
- C. Product Backlog ordering.
- D. Stakeholders for the Sprint Review.
- E. Sprint length.
Answer: A
Explanation:
Developers are self-managing, which means that they decide how much work they can do in a Sprint, and how they will do it1. They manage 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 create and update the Sprint Backlog throughout the Sprint as more is learned[3][3]. The other options are not managed by the Developers, but by the Product Owner or the Scrum Team as a whole. The Product Owner is accountable for ordering the Product Backlog, which is an ordered list of everything that is known to be needed in the product4. The Product Owner also decides when to release the product, based on the value, risk, and stakeholder feedback5. The Scrum Team collaborates on inviting the stakeholders for the Sprint Review, which is an event where the Scrum Team and the stakeholders inspect the product Increment and adapt the Product Backlog. The Scrum Team also decides the Sprint length, which is the time-box within which the Scrum Team delivers a product Increment.
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. 10
* 4: The Scrum Guide, November 2020, p. 6
* 5: Managing Products with Agility, Scrum.org, accessed on December 16, 2023
* : The Scrum Guide, November 2020, p. 13
* : The Scrum Guide, November 2020, p. 9
NEW QUESTION # 44
What typically happens if the Product Backlog is not sufficiently clear at Sprint Planning?
(choose the best answer)
- A. The Product Owner should select the Sprint Goal for the Scrum Team so that work can begin.
- B. Sprint Planning is canceled so refinement can be done first.
- C. Nothing in particular.
- D. The Scrum Master should not allow this to happen. Look for a new Scrum Master and re-start the Sprint.
- E. The Developers will find it difficult to create a Sprint forecast they are confident they can meet.
Answer: E
Explanation:
Explanation
If the Product Backlog is not sufficiently clear at Sprint Planning, the Developers will find it difficult to create a Sprint forecast they are confident they can meet. This is because:
* Sprint Planning is an event where the Scrum Team plans for the upcoming Sprint. The purpose of Sprint Planning is to align the entire Scrum Team around a common goal and a plan for delivering an Increment that meets that goal.
* The Developers are accountable for creating a Sprint forecast, which is a selection of Product Backlog items that they intend to work on during the Sprint. The Sprint forecast should be realistic, achievable, and valuable.
* The Product Owner is accountable for ensuring that the Product Backlog is transparent, visible, and understood by everyone who needs to work on it. They must collaborate with the Developers and provide clarifications, feedback, and guidance on what items are most important and valuable for the product.
* If the Product Backlog is not sufficiently clear at Sprint Planning, it means that there are items that are not well defined, ordered, or estimated. This may make it hard for the Developers to understand what they are supposed to build and why. It may also make it hard for them to estimate how much work they can do or how long it will take them to do it. This may result in a poor or inaccurate Sprint forecast that may affect the quality or value of the Increment.
Other options, such as the Product Owner selecting the Sprint Goal for the Scrum Team so that work can begin, nothing in particular happening, the Scrum Master not allowing this to happen or looking for a new Scrum Master and re-starting the Sprint, or Sprint Planning being canceled so refinement can be done first, are not valid answers as they do not reflect what typically happens or what should happen in Scrum.
References:
* [Scrum Guide], page 14, section "Sprint Planning"
* [Scrum Guide], page 7, section "Developers"
* [Scrum Guide], page 6, section "Product Owner"
* [Scrum Guide], page 11, section "Product Backlog"
NEW QUESTION # 45
What are two effective ways for a Scrum Team to ensure security concerns are satisfied? (choose the best two answers)
- A. Delegate the work to the security department.
- B. Add security concerns to the Definition of Done.
- C. Postpone the work until a specialist can perform a security audit and create a list of security-related Product Backlog items.
- D. Have the Scrum Team create Product Backlog items for each concern.
- E. Add a Sprint to specifically resolve all security concerns.
Answer: B,D
Explanation:
Explanation
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."
NEW QUESTION # 46
What is the accountability of the Product Owner during Sprint 0?
(choose the best answer)
- A. Create the overall release plan to ensure that organizational goals are met.
- B. Gathering, eliciting, and analyzing the requirements to build the Product Backlog.
- C. There is no such thing as Sprint 0.
- D. Determine the composition of the Scrum Team to meet the release plan.
- E. Make sure enough Product Backlog items are refined to fill the first 3 Sprints.
Answer: C
Explanation:
Explanation
Sprint 0 is a term that some organizations use to describe a phase of work before the first official Sprint, where they do some upfront planning, design, architecture, or analysis1. However, this term is not consistent with the Scrum framework, which does not prescribe any pre-Sprint activities or phases2. Scrum starts with a Product Backlog that contains at least one valuable and feasible Product Goal, and enough Product Backlog items to initiate the first Sprint[3][3]. The Product Owner is accountable for maximizing the value of the product and the work of the Developers, and for managing the Product Backlog4. The Product Owner does not have any specific accountability during Sprint 0, because Sprint 0 is not a part of Scrum.
References:
1: Sprint Zero: A Good Idea or Not?, Scrum Alliance, accessed on December 16, 2023
2: The Scrum Guide, November 2020, p. 5
[3][3]: The Scrum Guide, November 2020, p. 9
4: The Scrum Guide, November 2020, p. 6
NEW QUESTION # 47
Which two statements are correct when four teams are working on one single product?
- A. There can be 4 Product Owners.
- B. There can be 4 Product Backlogs.
- C. There can be only one Product Backlog.
- D. There can be only one Product Owner.
Answer: C,D
NEW QUESTION # 48
What does it mean for a Scrum Team to be cross-functional?
(choose the best answer)
- A. Developers on the Scrum Team work closely with business analysts, architects, developers, and testers who are not on the team.
- B. The Scrum Team includes skilled individuals who together have all the skills necessary to create value each Sprint.
- C. The Scrum Team includes not only developers but also business analysts, architects, and testers.
- D. The Scrum Team is a virtual team drawing from separate teams of business analysts, architects, developers, and testers.
Answer: B
Explanation:
The Scrum Team includes skilled individuals who together have all the skills necessary to create value each Sprint.
According to the Scrum Guide1, "Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint." This implies that the team does not depend on external resources or specialists to deliver a product increment. The other options do not reflect the true meaning of cross-functionality in Scrum.
1: The Scrum Team | Scrum.org
NEW QUESTION # 49
True or False: During the Sprint Review the stakeholder's role is to reorder the Product Backlog.
- A. False
- B. True
Answer: A
Explanation:
Explanation
During the Sprint Review, the stakeholder's role is not to reorder the Product Backlog, but rather to provide feedback and suggestions on the product and the process. Therefore, the answer is false because:
The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration. The stakeholders are invited to attend the Sprint Review as observers, participants, or customers, and they can share their opinions, ideas, or requests regarding the product and its features, functionality, quality, value, etc.
The ordering of the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions. The Product Owner may consider the feedback and suggestions from the stakeholders, as well as other factors such as dependencies, risks, costs, etc., when ordering the Product Backlog. However, they are not obliged to follow or implement them.
The Product Backlog is not a fixed or final list of requirements, but rather an emergent and dynamic artifact that represents all the possible changes to the product. The Product Owner is accountable for effective Product Backlog management, which includes refining, communicating, and optimizing the Product Backlog items. The Product Owner may update the Product Backlog at any time, not only during the Sprint Review.
References:
Scrum Guide 2020, page 11: "The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner." 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 15: "The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration."
NEW QUESTION # 50
Where is an evolving environment reflected in Scrum?
- A. In the Product Backlog.
- B. In the Scrum Team salary.
- C. In the number of Product Owners assigned to the Team.
Answer: A
NEW QUESTION # 51
Who determines how many Product Backlog items the Developers select for a Sprint?
(choose the best answer)
- A. The Product Owner.
- B. The Scrum Master.
- C. The Developers.
- D. The Scrum Team
- E. The stakeholders attending Sprint Planning.
Answer: C
Explanation:
Explanation
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].
References:
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
NEW QUESTION # 52
Following Scrum, only what has already happened may be used for forward-looking decision making.
- A. TRUE
- B. FALSE
Answer: A
NEW QUESTION # 53
What is a Product Owner typically responsible for during a Sprint?
(choose the best two answers)
- A. Creating financial reporting upon the spent hours reported by the Developers.
- B. Updating the work plan for the Developers on a daily basis.
- C. Collaborating with stakeholders, users, and customers.
- D. Nothing.
- E. Attending every Daily Scrum to answer questions about the Sprint Backlog items.
- F. Working with the Scrum Team on Product Backlog refinement.
Answer: C,F
Explanation:
* The 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 Sprint is a timebox of one month or less within which a "Done" product Increment is created. A Sprint consists of the Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective. A Sprint is also a feedback loop that allows the Scrum Team and the stakeholders to inspect and adapt the product and the process.
* During a Sprint, a Product Owner is typically responsible for:
* Collaborating with stakeholders, users, and customers: The Product Owner engages in frequent and regular interactions with the people who have a stake or interest in the product, such as customers, users, sponsors, managers, or other teams. The Product Owner solicits and incorporates their input, feedback, and insights to understand their needs and expectations, discover new opportunities or ideas, align and collaborate on the product direction and priorities, and validate and deliver value to them.
* Working with the Scrum Team on Product Backlog refinement: The Product Owner works closely with the Developers to clarify, refine, and review the Product Backlog items and their acceptance criteria. The Product Owner provides clear and concise descriptions of what is needed and why it is valuable for each Product Backlog item. The Product Owner also empowers and trusts the Developers to make technical decisions and trade-offs that best meet the product goals and quality standards. The Product Owner also involves key stakeholders in defining and prioritizing the Product Backlog items and their acceptance criteria.
* The other options are not valid or relevant responsibilities of a Product Owner during a Sprint. They are either too administrative, micromanaging, or unrelated to the product value delivery. They are:
* Creating financial reporting upon the spent hours reported by the Developers: This is not a responsibility of a Product Owner during a Sprint. This is an administrative task that does not contribute to the value or quality of the product or service delivered. It may also create unnecessary overhead or bureaucracy for the Developers. The Product Owner should focus on maximizing value rather than tracking hours.
* Updating the work plan for the Developers on a daily basis: This is not a responsibility of a
* Product Owner during a Sprint. This is a micromanaging task that does not respect the self-organization or cross-functionality of the Developers. The Developers are responsible for planning and executing their own work during a Sprint, based on their empirical experience and collaboration. The Developers also update their progress daily during the Daily Scrum event.
* Nothing: This is not a valid answer for a Product Owner's responsibility during a Sprint. A Product Owner has many important responsibilities during a Sprint, as mentioned above. A Product Owner should be actively involved in collaborating with stakeholders, users, customers, and Developers throughout a Sprint to maximize value delivery.
* Attending every Daily Scrum to answer questions about the Sprint Backlog items: This is not a mandatory responsibility of a Product Owner during a Sprint. The Daily Scrum is an event for the Developers to inspect their progress toward the Sprint Goal and adapt their plan for the next 24 hours. The Daily Scrum is not a status meeting or a reporting session for anyone else. The Product Owner may attend the Daily Scrum as an observer or as an invited participant if they have something valuable to contribute or if they need some clarification from the Developers.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
* Sprint: https://www.scrum.org/resources/what-is-a-sprint-in-scrum
* Stakeholders: https://www.agilealliance.org/glossary/stakeholders
* Daily Scrum: https://www.scrum.org/resources/what-is-a-daily-scrum
NEW QUESTION # 54
Who starts the Daily Scrum?
(choose the best answer)
- A. The Product Owner.
- B. Whoever the Developers decide should start.
- C. The Scrum Master. This ensures that the Developers have the event, and it stays within the timebox.
- D. The person who has the token.
- E. The person coming in last. This encourages people to be on time and helps to stay within the timebox.
Answer: B
Explanation:
The Daily Scrum is an event for and by the Developers. They can choose whatever structure and technique they want, as long as they focus on the progress toward the Sprint Goal and produce an actionable plan for the next day of work12. The Scrum Master, the Product Owner, and the person coming in last are not necessarily the ones who should start the Daily Scrum. The person who has the token is a possible technique, but not the only one3.
NEW QUESTION # 55
Scrum is based on empiricism. All of its artifacts must be transparent to ensure sufficient accuracy of inspection. How can the Scrum Team maintain the Product Backlog to maximize its transparency?
(choose the best answer)
- A. Product Backlog items must be sized such that the highest ordered items are no bigger than a Sprint.
- B. Product Backlog items should hold no more than 8 points of work, which is the average in the range of acceptable sizes of 1, 2, 3, 5, 8, and 13.
- C. The Product Backlog is only updated at a release planning meeting with the stakeholders and the change control board present.
- D. The Product Backlog is continually kept up to date with the most recent insights.
- E. The Product Backlog is only updated at the Sprint Review, when both the Scrum Team and the stakeholders are available.
Answer: D
Explanation:
Explanation
The Scrum Team can maintain the Product Backlog to maximize its transparency by continually keeping it up to date with the most recent insights because:
It reflects the current state of the product and the work. The Product Backlog is a dynamic and emergent artifact that represents all the possible features, functions, requirements, enhancements, and fixes that constitute changes to the product. By updating it frequently, the Scrum Team can ensure that the Product Backlog is accurate, complete, and relevant.
It enables the Product Owner to optimize the value of the product and the work of the Scrum Team. The Product Owner is accountable for effective Product Backlog management, which includes ordering, refining, and communicating the Product Backlog items. By updating it frequently, the Product Owner can incorporate new learnings, feedback, opportunities, and changes into the product decisions and priorities.
It supports the inspection and adaptation of the Scrum Team and the stakeholders. The Product Backlog is a source of information and transparency for everyone involved in the product development. By updating it frequently, the Scrum Team and the stakeholders can inspect the progress and outcomes of each Sprint, and adapt their plans and actions accordingly.
References:
Scrum Guide 2020, page 10: "The Product Backlog is an emergent, ordered list of what is needed to improve the product." Scrum Guide 2020, page 11: "The Product Owner is accountable for effective Product Backlog management, which includes ... ensuring that the Product Backlog is transparent, visible and understood." Scrum Guide 2020, page 11: "The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions." Scrum Guide 2020, page 11: "Higher ordered Product Backlog items are clearer and more refined than lower ordered ones." Scrum Guide 2020, page 15: "The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration."
NEW QUESTION # 56
True or False: A Product Owner should measure product value by the increase in the team's velocity.
- A. False
- B. True
Answer: A
Explanation:
Explanation
A Product Owner should not measure product value by the increase in the team's velocity. This is because:
* Velocity is a measure of how much work a Scrum Team can deliver in a Sprint. It is based on the estimation of Product Backlog items that are selected for a Sprint and completed according to the Definition of Done.
* Velocity is not a measure of product value. It does not reflect how well the product meets the needs and expectations of the customers, users, and stakeholders. It does not reflect how much value or impact the product creates in terms of revenue, satisfaction, or social good.
* Velocity is not a goal or a target for a Scrum Team. It is a planning tool that helps them forecast their future work based on their past performance. It is not a metric that should be used to compare or judge teams or individuals.
* A Product Owner should measure product value by using indicators that are relevant, meaningful, and actionable for their product context. These may include metrics such as customer feedback, usage data, market share, return on investment, or social impact.
References:
* [Scrum Guide], page 7, section "Developers"
* [Scrum Guide], page 10, section "Definition of Done"
* [Scrum Guide], page 15, section "Sprint Backlog"
* [Professional Scrum Product Owner Training], page 5, section "Product Value"
* [Professional Scrum Product Owner Training], page 9, section "Business Strategy"
NEW QUESTION # 57
......
Authentic Best resources for PSPO-I Online Practice Exam: https://www.prep4pass.com/PSPO-I_exam-braindumps.html
Get the superior quality PSPO-I Dumps with explanations waiting just for you, get it now: https://drive.google.com/open?id=1bkj2pSEGQmyBDjrYdqtwpQprGOL6JbaF
