What is the purpose of a Sprint Review?(choose the best answer)
Answer(s): C
The Sprint Review is an event that occurs at the end of each Sprint, where the Scrum Team and the stakeholders inspect the Increment and adapt the Product Backlog if needed. The Sprint Review is an opportunity for the Product Owner to validate that the Increment meets their expectations and delivers value to the customers and users. The Sprint Review is also an opportunity for the Developers to demonstrate their work and receive feedback from the Product Owner and the stakeholders.The purpose of a Sprint Review is to inspect the product Increment with the stakeholders and collect feedback on next steps. The Sprint Review is a collaborative and interactive session where the Scrum Team and the stakeholders discuss what was done in the Sprint, what problems were encountered, what was learned, and what can be improved or changed. The Sprint Review also provides input for updating the Product Backlog to maximize value in future Sprints. The other options are not valid or relevant purposes of a Sprint Review. They are either too vague, unrelated, or incorrect. They are:To build team spirit: This is not a valid purpose of a Sprint Review. While team spirit is important for any Scrum Team, it is not the main focus or outcome of a Sprint Review. A Sprint Review is a formal event that has a specific agenda and goal, not a casual or social gathering. To take time to judge the validity of the project: This is not a valid purpose of a Sprint Review. Scrum does not have a concept of a project, but rather a product. A product is a valuable solution that evolves over time to meet customer needs and market conditions. A project is a temporary endeavor with a fixed scope, time, and cost. A Sprint Review is not a time to judge or evaluate the validity of the product or its development, but rather to inspect and adapt it based on empirical evidence and feedback.To review the Scrum Team's activities and processes during the Sprint: This is not a valid purpose of a Sprint Review. This is the purpose of another Scrum event called the Sprint Retrospective. The Sprint Retrospective is an event that occurs after the Sprint Review and prior to the next Sprint Planning, where the Scrum Team inspects how they worked during the Sprint and identifies improvements for the next Sprint. The Sprint Retrospective focuses on improving the Scrum Team's performance and process, not on inspecting the product Increment or its value.
Scrum Guide: https://www.scrumguides.org/scrum-guide.html Sprint Review: https://www.scrum.org/resources/what-is-a-sprint-review
The IT manager asks a Scrum Team for a status report describing the progress throughout the Sprint. The Scrum Team asks the Scrum Master for advice. The Scrum Master should:(choose the best answer)
Answer(s): E
The Scrum Master should talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review. This is because:The Scrum Team is self-managing and does not need to report to anyone outside the team1. The Sprint Review is an event where the Scrum Team and the stakeholders collaborate on the product and inspect the Increment2.The Increment is a concrete and usable outcome of the Sprint that provides a measure of progress and value delivery3.The IT manager can attend the Sprint Review as a stakeholder and provide feedback on the product and the process4.
Scrum Guide, page 7, section "The Scrum Team"Scrum Guide, page 13, section "Sprint Review"Scrum Guide, page 10, section "Increment"Scrum Guide, page 14, section "Sprint Review"
Which metrics will help a Product Owner determine if a product is delivering value? (choose the best two answers)
Answer(s): A,D
The metrics that will help a Product Owner determine if a product is delivering value are customer satisfaction and time to market. This is because:Customer satisfaction is a measure of how well the product meets the needs and expectations of the customers5. It reflects the value proposition of the product and the feedback from the users. Time to market is a measure of how quickly the product can be delivered to the market. It reflects the agility and responsiveness of the Scrum Team and the ability to deliver value early and often. Other metrics, such as productivity, velocity, and percentage of scope implemented, are not directly related to value delivery. They may indicate how efficiently or effectively the Scrum Team is working, but they do not necessarily reflect how valuable or desirable the product is for the customers or stakeholders.
Professional Scrum Product OwnerTM Training, page 5, section "Product Value" Professional Scrum Product OwnerTM Training, page 6, section "Product Vision" Professional Scrum Product OwnerTM Training, page 7, section "Product Backlog Management" Professional Scrum Product OwnerTM Training, page 8, section "Release Management" Professional Scrum Product OwnerTM Training, page 9, section "Business Strategy" Professional Scrum Product OwnerTM Training, page 10, section "Stakeholders & Customers"
If Product Backlog refinement is needed, when is the ideal time for refinement to take place and who should participate?(choose the best two answers)
Answer(s): A,E
The ideal time for refinement to take place and who should participate are the Scrum Team during the current Sprint, if they have been unable during preceding Sprints to define Product Backlog items with enough precision to begin work, and the Scrum Team on an ongoing basis, defining Product Backlog items into smaller more precise items that are ready for selection. This is because:Product Backlog refinement is the act of adding detail, estimates, and order to Product Backlog items. It is an ongoing and collaborative process that involves the whole Scrum Team.The Scrum Team should refine the Product Backlog as needed to ensure that there are enough items that are sufficiently clear and ready for selection in Sprint Planning. The amount of time spent on refinement usually varies from one Scrum Team to another, but it is recommended not to exceed 10% of the capacity of the Developers.The Scrum Team may also use a Sprint to refine the Product Backlog if they have not been able to do so in previous Sprints. This may happen when the product is new or complex, or when there is a significant change in the product vision or direction. However, this should be an exception rather than a rule, as it may delay the delivery of value and feedback. Other options, such as business analysts doing the refinement work for the Scrum Team, the Product Owner doing the refinement alone in Sprint 0 or between Sprints, or handing off the ownership of the Product Backlog to someone else, are not consistent with the principles and values of Scrum. They may lead to misunderstandings, misalignment, or loss of ownership and accountability.
[Scrum Guide], page 11, section "Product Backlog"[Scrum Guide], page 12, section "Product Backlog Refinement" [Professional Scrum Product OwnerTM Training], page 7, section "Product Backlog Management" [Professional Scrum Product OwnerTM Training], page 8, section "Release Management" [Professional Scrum Product OwnerTM Training], page 9, section "Business Strategy"
What are three advantages of a Product Owner sharing a clearly defined Product Goal with the Scrum Team?(choose the best three answers)
Answer(s): C,D,E
The advantages of a Product Owner sharing a clearly defined Product Goal with the Scrum Team are:It provides a good overall direction so Sprints will feel less like isolated pieces of work. The Product Goal is a long-term objective for the product that guides all the activities of the Scrum Team. It helps the Scrum Team align their efforts and focus on delivering value that contributes to the product vision.It helps the Scrum Team keep focus and they can weigh any decision against the Product Goal. The Product Goal serves as a filter for deciding what to work on and what not to work on. It helps the Scrum Team prioritize and optimize their work based on value and impact. It is easier to inspect incremental progress at the Sprint Review. The Sprint Review is an event where the Scrum Team and the stakeholders collaborate on the product and inspect how it meets the Product Goal. The Increment is a concrete and usable outcome of the Sprint that provides a measure of progress towards the Product Goal.Other options, such as helping the Developers estimate the date that the Product Backlog will be complete or being not mandatory in Scrum, are not valid advantages of having a Product Goal. They may reflect a misunderstanding of what a Product Goal is or how Scrum works.
[Scrum Guide], page 10, section "Product Goal"[Professional Scrum Product OwnerTM Training], page 6, section "Product Vision" [Professional Scrum Product OwnerTM Training], page 7, section "Product Backlog Management" [Scrum Guide], page 13, section "Sprint Review"[Scrum Guide], page 10, section "Increment"
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.