Pass4Future also provide interactive practice exam software for preparing Scrum Professional Scrum Product Owner I (PSPO-I) Exam effectively. You are welcome to explore sample free Scrum PSPO-I Exam questions below and also try Scrum PSPO-I Exam practice test software.
Do you know that you can access more real Scrum PSPO-I exam questions via Premium Access? ()
When does a Developer become accountable for the value of a Product Backlog item selected for the Sprint?
(choose the best answer)
Answer : D
Correct Answer: D) Never. The entire Scrum Team is accountable for creating
According to the Scrum Guide, the Scrum Team consists of one Product Owner, one Scrum Master, and Developers. The Scrum Team is responsible for all product-related activities, including delivering a valuable, usable product increment every Sprint. The Product Owner is accountable for maximizing the value of the product and the work of the Developers. The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog; instilling quality by adhering to a Definition of Done; and adapting their plan each day toward the Sprint Goal. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, helping everyone understand Scrum theory and practice, and removing impediments to the Scrum Team's progress.
Therefore, the Developers are not individually accountable for the value of a Product Backlog item selected for the Sprint, but collectively accountable as part of the Scrum Team. The value of a Product Backlog item is determined by the Product Owner, who orders the Product Backlog items based on stakeholder needs and feedback. The Developers collaborate with the Product Owner to understand the value and requirements of each Product Backlog item and deliver a potentially releasable product increment that meets the Definition of Done and the Sprint Goal.
[Scrum Guide], section 2.2: ''The Scrum Team is responsible for all product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else that might be required.''
Accountabilities in Scrum | Scrum.org: ''Scrum has three accountabilities, each with a different focus : Product Owner (green figure) The 'What'. With a focus on Value, time to market, return on investment and Total Cost of Ownership (TCO). Developers (red figures) The 'How'. Focus on building something that is Done -- that the increment is useable and potentially releasable.''
What is a Developer in Scrum? | Scrum.org: ''The specific skills needed by the Developers are often broad and will vary based on the type of work they are doing. However, the Developers are always accountable for: Creating a plan for the Sprint, the Sprint Backlog Instilling quality by adhering to a Definition of Done Adapting their plan each day toward the Sprint Goal''
In the middle of the Sprint, the customer decides that there are two new features she wants.
The Product Owner could:
(choose the best two answers)
Answer : B, C
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.
The Developers are accountable for creating a ''Done'' Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.
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.
The Sprint Goal is a short statement of what the Scrum Team intends to achieve during a Sprint. It provides guidance and direction for the Scrum Team, as well as a basis for inspecting and adapting the product and the process. The Sprint Goal is aligned with the product vision and goals, and it reflects the value and purpose of the Sprint.
In the middle of a Sprint, if a customer decides that there are two new features she wants, there are two possible ways that a Product Owner could handle this situation:
Ask the Developers to consider whether they can add these features to the current Sprint without endangering the Sprint Goal: The Product Owner could discuss with the Developers if they have enough capacity and skills to accommodate these new features in their current Sprint Backlog. The Product Owner could also explain why these features are valuable or urgent for the customer or user. The Developers could then decide if they can or want to add these features to their current work plan, or if they prefer to defer them to a future Sprint. The Developers should not compromise on quality or scope to fit these features in their current Sprint. The Developers should also ensure that these features are aligned with or support the current Sprint Goal.
Add these features to the Product Backlog: The Product Owner could add these new features to the Product Backlog as new items. The Product Owner could then order these items based on their value, risk, priority, dependency, feedback, or market conditions. The Product Owner could also refine these items with more details or acceptance criteria. The Product Owner could then plan to include these items in a future Sprint, depending on their order and availability.
The other options are not valid or relevant ways that a Product Owner could handle this situation. They are either too disruptive, impractical, or irrelevant. They are:
Introduce these features at the next Daily Scrum: This is not a valid way for a Product Owner to handle this situation. 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. However, introducing new features at this event would be disruptive and inappropriate for both parties.
Have the Scrum Master add these features to the current Sprint: This is not a valid way for a Product Owner to handle this situation. The Scrum Master is not responsible for adding or removing any work from the current Sprint. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. The Scrum Master does this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.
Scrum Guide: https://www.scrumguides.org/scrum-guide.html
Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
Sprint: https://www.scrum.org/resources/what-is-a-sprint-in-scrum
Sprint Goal: https://www.scrum.org/resources/what-is-a-sprint-goal
Daily Scrum: https://www.scrum.org/resources/what-is-a-daily-scrum
Scrum Master: https://www.scrum.org/resources/what-is-a-scrum-master
Why is the Daily Scrum held at the same time and same place?
(choose the best answer)
Answer : D
The Daily Scrum is held at the same time and same place because:
The consistency reduces complexity. By having a fixed time and place for the Daily Scrum, the Developers can avoid wasting time and energy on scheduling, logistics, or coordination issues. They can also establish a routine and a rhythm that helps them focus on their work and their Sprint Goal.
The consistency increases transparency. By having a fixed time and place for the Daily Scrum, the Developers can ensure that everyone is aware of when and where the meeting takes place, and that everyone has an opportunity to participate and share their progress, plans, and challenges. They can also invite other stakeholders or observers, if they find it useful, to provide feedback or support.
The consistency enhances collaboration. By having a fixed time and place for the Daily Scrum, the Developers can create a safe and comfortable space for them to communicate, interact, and collaborate with each other. They can also build trust, rapport, and accountability among themselves, and foster a sense of team spirit and ownership.
Scrum Guide 2020, page 12: ''The Daily Scrum is held at the same time and place each day to reduce complexity.''
Scrum Guide 2020, page 12: ''The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.''
Scrum Guide 2020, page 13: ''The Daily Scrum is an internal meeting for the Developers. If others are present, the Scrum Master ensures that they do not disrupt the meeting.''
True or False: Every Scrum Team must have a Product Owner and Scrum Master.
Answer : D
The Product Owner and the Scrum Master are essential roles in the Scrum Team. They have distinct accountabilities and responsibilities that contribute to the success of the product and the team. The Product Owner is responsible for maximizing the value of the product and the work of the Developers. The Scrum Master is responsible for promoting and supporting Scrum and the Scrum Team. Both roles need to be fully engaged and available to the Scrum Team throughout the Sprint.
Who is responsible for the sizing of Product Backlog items?
(choose the best answer)
Answer : D
According to Scrum.org, the Developers who will be doing the work are responsible for the sizing of Product Backlog items1. The Product Owner may influence the Developers by helping them understand and select trade-offs1. This implies that the Developers size the items after clarifying requirements with the Product Owner1.
