[2023] New PSPO-I exam Free Sample Questions to Practice [Q179-Q196]

* The best statement that describes Scrum is: A framework to generate value through adaptive solutions for complex problems.
* Scrum is a lightweight framework that helps people, teams, and organizations to deliver valuable products in complex and uncertain environments.
* Scrum is based on empiricism, which means that knowledge comes from experience and making decisions based on what is observed. Scrum employs an iterative and incremental approach to optimize predictability and control risk.
* Scrum is not a defined and predictive process, a complete methodology, or a cookbook that defines best practices. Scrum provides the minimal boundaries within which teams can self-organize and create innovative solutions. References: Scrum Guide, Section 1 (Definition of Scrum) and Section 2 (Uses of Scrum)

Explanation
Scrum does not require that the Product Owner must use any of the following items:
* Burndown chart: A burndown chart is a graphical representation of work left to do versus time. It can be used to track progress and forecast completion dates of projects or Sprints. However, it is not mandatory or prescribed in Scrum. It is one of the possible techniques that a Product Owner may use to monitor and communicate product development.
* Feature burn-up: A feature burn-up chart is a graphical representation of features completed versus time.
It can be used to track progress and forecast scope changes of projects or Sprints. However, it is not mandatory or prescribed in Scrum. It is one of the possible techniques that a Product Owner may use to monitor and communicate product development.
* Critical Path Analysis: Critical Path Analysis is a project management technique that identifies the sequence of tasks that must be completed on time for a project or Sprint to finish on schedule. It can be used to plan, monitor, and control complex projects or Sprints. However, it is not mandatory or prescribed in Scrum. It is one of the possible techniques that a Product Owner may use to manage product development.
* Project Gantt chart: A project Gantt chart is a graphical representation of tasks, dependencies, durations, and milestones of a project or Sprint. It can be used to plan, monitor, and control complex projects or Sprints. However, it is not mandatory or prescribed in Scrum. It is one of the possible techniques that a Product Owner may use to manage product development.
Therefore, the correct answer is none of the above.
References:
* [Scrum Guide], page 6, section “Product Owner”
* [Scrum Guide], page 11, section “Product Backlog”
* [Professional Scrum Product Owner Training], page 8, section “Release Management”

Explanation
* In Scrum, there is only one product and one Product Backlog for a given product. The Product Backlog is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes, and anything else that can deliver value to the customers and users of the product. The Product Backlog is ordered by the Product Owner based on the product vision, goals, and value.
* Having multiple Product Backlogs for one product would create confusion, duplication, inconsistency, and waste. It would also make it harder to align the Scrum Teams and the stakeholders on the same product direction and priorities. Therefore, each Scrum Team should not have a separate Product Backlog.
* 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.
* Having multiple Product Owners for one product would create conflicts, overlaps, gaps, and inefficiencies. It would also make it harder to maintain a clear and consistent product vision, strategy, roadmap, and backlog. Therefore, there should be only one Product Owner for one product.
* In some cases, when there are multiple Scrum Teams working on one product, it may be necessary to have some form of scaling or coordination mechanism to ensure alignment and collaboration among the teams. However, this does not mean that there should be multiple Product Owners or Product Backlogs.
Instead, there should be ways to facilitate communication, feedback, integration, and transparency among the teams and with the Product Owner. For example, some frameworks or practices that can help with scaling Scrum are Nexus, LeSS, SAFe, or Scrum of Scrums.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Nexus: https://www.scrum.org/resources/what-is-nexus
* LeSS: https://less.works/
* SAFe: https://www.scaledagileframework.com/
* Scrum of Scrums: https://www.agilealliance.org/glossary/scrum-of-scrums/

Explanation
It is not true that a Product Owner must create clear and unambiguous acceptance criteria for each Product Backlog item before it may be selected in Sprint Planning. This is because:
* Acceptance criteria are a set of conditions that a Product Backlog item must satisfy to be accepted by the Product Owner or the stakeholders. They are used to verify that the item meets the expected quality and value standards.
* Acceptance criteria are not mandatory or prescribed in Scrum. They are one of the possible techniques
* that a Product Owner may use to communicate their expectations and requirements to the Developers and the stakeholders. They are not part of the Scrum Guide or the Definition of Done.
* Acceptance criteria do not need to be created before Sprint Planning. They can be created or refined at any time during the product development process, as long as they are clear and agreed upon before the item is considered complete. They can also be changed or updated based on feedback or new insights.
* The only requirement for a Product Backlog item to be selected in Sprint Planning is that it is sufficiently clear and ready for selection. This means that it has enough detail and precision for the Developers to understand what they are supposed to build and why. It also means that it has been refined and ordered by the Product Owner based on value and impact.
References:
* [Scrum Guide], page 14, section “Sprint Planning”
* [Scrum Guide], page 12, section “Product Backlog Refinement”
* [Professional Scrum Product Owner Training], page 7, section “Product Backlog Management”

Explanation
* The Product Owner is one person, not a committee or a team of people. 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.
* Having multiple Product Owners for one product would create conflicts, overlaps, gaps, and inefficiencies. It would also make it harder to maintain a clear and consistent product vision, strategy,
* roadmap, and backlog. Therefore, the Scrum Team can not have multiple Product Owners.
* The Product Owner is accountable for ordering the Product Backlog. The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes, and anything else that can deliver value to the customers and users of the product. The Product Owner orders the items in the Product Backlog based on factors such as value, risk, priority, dependency, feedback, or market conditions.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
* Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog