Ask Question
Scrum PSPO-I Practice Test - Questions Answers
Question list
List of questions
Related questions
Question 1
The job of a Product Owner focuses on the following:
(choose the best two answers)
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.
The job of a Product Owner focuses on the following aspects:
Working with customers and stakeholders to identify the most valuable product requirements: 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. The Product Owner translates these requirements into Product Backlog items that can deliver value to customers or users.
Clearly communicating project or release status and strategies to customers and stakeholders: The Product Owner communicates effectively and transparently with the customers and stakeholders about the progress, outcomes, and plans of the product development. The Product Owner shares relevant information and data about the product vision, goals, value proposition, roadmap, backlog, increment, feedback, or metrics. The Product Owner also communicates the strategies and decisions for delivering value to customers or users, such as release frequency, scope, quality, or risk management.
The other options are not valid or relevant aspects of a Product Owner's job. They are either too narrow, unrealistic, or unrelated to the product value delivery. They are:
Writing clear, transparent User Stories: This is not a valid aspect of a Product Owner's job. User Stories are a common format for expressing product requirements in an agile way. They consist of a brief description of a feature or function from the perspective of a user or customer. They usually follow a template such as "As a <role>, I want <goal>, so that <benefit>". However, User Stories are not mandatory or universal in Scrum. The Product Owner can use any format or method to express product requirements, as long as they are clear, concise, and valuable. The format or method does not affect the value or quality of the product or service delivered.
Being with the Scrum Team all the time, just in case they need me to clarify a requirement: This is not a realistic aspect of a Product Owner's job. The Product Owner does not have to be physically present with the Scrum Team all the time. The Product Owner can work remotely or asynchronously with the Scrum Team, as long as they maintain effective communication and collaboration. The Product Owner should also empower and trust the Developers to make technical decisions and trade-offs that best meet the product goals and quality standards. The Product Owner should also ensure that the Product Backlog items are sufficiently clear and refined before they are selected for a Sprint.
Scrum Guide: https://www.scrumguides.org/scrum-guide.html
Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
User Stories: https://www.agilealliance.org/glossary/user-stories
Question 2
Who determines when it is appropriate to update the Sprint Backlog during a Sprint?
(choose the best answer)
Explanation:
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint, and it belongs solely to the Developers.
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.
The Developers are also responsible for updating the Sprint Backlog throughout the Sprint. The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum. The Developers modify the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Developers work through the plan and learn more about the work needed to achieve the Sprint Goal.
As new work is required, the Developers add it to the Sprint Backlog. As work is performed or completed, the estimated remaining work is updated. When elements of the plan are deemed unnecessary, they are removed. Only the Developers can change its content and order during a Sprint.
Scrum Guide: https://www.scrumguides.org/scrum-guide.html
Sprint Backlog: https://www.scrum.org/resources/what-is-a-sprint-backlog
Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
Question 3
What is the timebox for the Sprint Planning event?
(choose the best answer)
Explanation:
The Sprint Planning is an event that occurs at the beginning of each Sprint, where the Scrum Team plans how to deliver a valuable product Increment. The Sprint Planning consists of two topics: What can be done this Sprint? and How will the chosen work get done? The outcome of the Sprint Planning is an agreed-upon Sprint Goal, a Sprint Backlog, and a plan for delivering the Increment.
The timebox for the Sprint Planning event is proportional to the length of the Sprint. For a one-month Sprint, the timebox is 8 hours. For shorter Sprints, the timebox is usually shorter. The Scrum Team may decide how much time to spend on each topic within the timebox, depending on their needs and preferences.
The timebox for the Sprint Planning event ensures that the Scrum Team does not spend too much or too little time on planning their work for the Sprint. The timebox also ensures that the Scrum Team has enough clarity and alignment on what and how they want to achieve during the Sprint.
Scrum Guide: https://www.scrumguides.org/scrum-guide.html
Sprint Planning: https://www.scrum.org/resources/what-is-sprint-planning
Question 4
The Scrum Team should have all the skills needed to:
(choose the best answer)
Explanation:
The Scrum Team should have all the skills needed to turn Product Backlog items into a valuable, useful Increment, as this is the primary goal of each Sprint. The Scrum Guide states that '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.'1The Scrum Team should be cross-functional, which means that the Developers have all the skills necessary to create a product Increment.1The Scrum Team should also be self-managing, which means that they decide how best to accomplish their work, rather than being directed by others outside the Scrum Team.1
1: The Scrum Guide2, page 6
2:The Scrum Guide
Question 5
How often should Scrum Team membership change?
(choose the best answer)
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.'1Therefore, the Scrum Team should consider the impact of changing its membership on its productivity and performance, and balance the need for stability and flexibility.
1: The Scrum Guide2, page 6
2:The Scrum Guide
Question 6
For the purpose of transparency, when does Scrum say a valuable and useful Increment must be available?
(choose the best answer)
Explanation:
The Scrum Guide states that 'The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints.At the end of a Sprint, the new Increment must be 'Done,' which means it must be in useable condition and meet the Scrum Team's definition of 'Done."1This means that a valuable and useful Increment must be available at the end of every Sprint, regardless of the release frequency or the Product Owner's request. This ensures transparency, feedback, and continuous improvement.
1: The Scrum Guide2, page 14
2:The Scrum Guide
Question 7
The timebox for a Daily Scrum is?
(choose the best answer)
Explanation:
The Scrum Guide states that 'The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours.'1The Daily Scrum is a quick and simple planning meeting designed to keep everyone in the loop with how other team members are getting on. It ensures that team members are fully aligned with each other and on track to hit the Sprint Goal.
1: The Scrum Guide2, page 11
2:The Scrum Guide
Question 8
Which statement best describes the Sprint Backlog as the output of the Sprint Planning?
(choose the best answer)
Explanation:
The Sprint Backlog is the output of the Sprint Planning, where the Developers select the Product Backlog items that they can deliver in the Sprint and create a plan for how to do the work.The Scrum Guide states that 'The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).'1The Sprint Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned.The Sprint Backlog makes visible all the work that the Developers identify as necessary to meet the Sprint Goal.1
1: The Scrum Guide2, page 15
2:The Scrum Guide
Question 9
When is the Sprint Backlog created?
(choose the best answer)
Explanation:
The Sprint Backlog is created during Sprint Planning, where the Developers select the Product Backlog items that they can deliver in the Sprint and create a plan for how to do the work.The Scrum Guide states that 'The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).'1The Sprint Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned.
1: The Scrum Guide2, page 15
2:The Scrum Guide
Question 10
A Sprint Retrospective should be held:
(choose the best answer)
Explanation:
The Sprint Retrospective is a time-boxed event for the Scrum Team to inspect how the last Sprint went and plan for improvements in the next Sprint. The Scrum Guide states that 'The Sprint Retrospective concludes the Sprint. It is timeboxed to a maximum of three hours for a one-month Sprint.For shorter Sprints, the event is usually shorter.'1This means that the Sprint Retrospective should be held at the end of each Sprint, regardless of the project or release status.The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements, including to product quality and working relationships.1
1: The Scrum Guide2, page 16
2:The Scrum Guide
Question