A Product Backlog is:(choose the best three answers)
Answer(s): B,C,D
A Product Backlog is:Managed by the Product Owner. 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.An inventory of things to be done for the Product. The Product Backlog contains all the features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases. The Product Backlog items have a description, an order, an estimate, and a value.Ordered based on priority, value, dependencies, and risk. The Product Owner orders the Product Backlog items based on various factors that affect their importance and urgency for the product. These may include customer needs, business value, stakeholder feedback, technical dependencies, or market opportunities.Other options, such as an exhaustive list of upfront approved requirements to be implemented or only visible to the Product Owner and stakeholders, are not valid descriptions of a Product Backlog. They may reflect a misunderstanding of what a Product Backlog is or how Scrum works.
[Scrum Guide], page 6, section "Product Owner"[Scrum Guide], page 11, section "Product Backlog"[Professional Scrum Product OwnerTM Training], page 7, section "Product Backlog Management"
True or False: Product Owners must create clear and unambiguous acceptance criteria for each Product Backlog item before it may be selected in Sprint Planning.
Answer(s): B
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.
[Scrum Guide], page 14, section "Sprint Planning"[Scrum Guide], page 12, section "Product Backlog Refinement" [Professional Scrum Product OwnerTM Training], page 7, section "Product Backlog Management"
Why do the Developers need a Sprint Goal?(choose the best answer)
Answer(s): C
The Developers need a Sprint Goal because it gives them a common yet specific goal to focus on during the Sprint. 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 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 need a Sprint Goal to align their efforts and collaborate effectively as a team. The Sprint Goal helps them prioritize and optimize their work based on value and impact. The Sprint Goal also helps them cope with uncertainty and complexity by providing a clear direction and a shared purpose.Other options, such as a Sprint Goal only giving purpose to Sprint 0, Sprint Goals being not valuable, or a Sprint Goal ensuring that all of the Product Backlog items selected for the Sprint are implemented, are not valid reasons why the Developers need a Sprint Goal. They may reflect a misunderstanding of what a Sprint Goal is or how Scrum works.
[Scrum Guide], page 15, section "Sprint Goal"[Scrum Guide], page 7, section "Developers"[Scrum Guide], page 10, section "Definition of Done"[Scrum Guide], page 10, section "Increment"
True or False: The Sprint Backlog is a result of Sprint Planning, and it includes the Sprint Goal.
Answer(s): A
It is true that the Sprint Backlog is a result of Sprint Planning, and it includes the Sprint Goal. 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 Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering them as a "Done" Increment. The Sprint Backlog is owned by the Developers who use it to organize and manage their work during the Sprint.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 Sprint Backlog is created by the collaborative work of the entire Scrum Team during Sprint Planning. The Product Owner proposes how the product could increase its value and utility in the current Sprint. The Developers discuss how they can deliver a "Done" Increment that meets this proposal. Together, they define a Sprint Goal that summarizes why the Sprint is valuable to stakeholders. Then, they select enough Product Backlog items from the top of the ordered Product Backlog to satisfy the Sprint Goal. Finally, they create a plan for how they will deliver those items as a "Done" Increment.
[Scrum Guide], page 14, section "Sprint Planning"[Scrum Guide], page 15, section "Sprint Backlog"[Scrum Guide], page 15, section "Sprint Goal"
Scrum requires that the Product Owner must use which of the following items? (choose all that apply)
Answer(s): E
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.
[Scrum Guide], page 6, section "Product Owner"[Scrum Guide], page 11, section "Product Backlog"[Professional Scrum Product OwnerTM Training], page 8, section "Release Management"
Post your Comments and Discuss Scrum PSPO I exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the PSPO I content, but please register or login to continue.