The Professional Scrum Product Owner (PSPO I) practice assessment is available to anyone who would like some help preparing for the official Scrum.org PSPO I assessment.
This practice assessment has been created by the Red Tangerine Team and it is not endorsed by Scrum.org.
As well as taking the practice assessment, we recommend doing the following to prepare for the Scrum.org PSPO I assessment:
This practice assessment consists of 20 questions to be answered in 20 minutes, with a pass mark of 85%.
Select all that apply:
Meeting customer’s and user’s needs, their desired outcomes and solving their problems in a way that results in an overall positive impact for the organisation is a far better measure of success.
The Daily Scrum is the Scrum event for the Developers to focus on progress towards the Sprint Goal and produce an actionable plan for the next day of work.
Scrum is designed for complex, uncertain environments. The regular cadence of Sprints and the feedback loops given by the Scrum events enable iterative and incremental learning, enabling options for how to proceed to emerge.
The entire organisation should respect the decisions of the Product Owner which are made transparent by the contents and ordering of the Product Backlog. Stakeholders should consult and convince the Product Owner if they want the Product Backlog to be changed. No changes should be made during a Sprint that endangers the Sprint Goal.
The Daily Scrum is an event for the Developers of the Scrum Team. The Developers self-manage, inspecting progress towards the Sprint Goal and producing an actionable plan for the next day of work.
Select all that apply:
There is no one best way to order the Product Backlog and different techniques will be more suitable to some contexts than others. The Product Owner has the accountability to maximise value, so they have the final say on the Product Backlog, regardless of any technique employed.
Further innovation in Product A is unlikely to result in additional value as it already has the majority of market share in comparison to Product B where innovation could lead to the capture of more market share.
Multiple Increments may be created and released during a Sprint. The Sprint Review should never be considered as a gate to releasing value. For an Increment to be releasable it must meet the Definition of Done.
Select all that apply:
The Product Backlog contains everything that is known to be needed to improve the product.
The Product Owner is part of the Scrum Team and as such shares in the Scrum Team’s successes, shortcomings and improvement actions. If the Developers are uncomfortable with the Product Owner being in the Sprint Retrospective, this should be considered as an impediment to be resolved.
The Developers are accountable for managing, executing and monitoring the plan for the Sprint. This plan is made transparent in the Sprint Backlog.
The Product Owner is one person, not a committee. There should be just one Product Backlog for a product, and one Product Owner accountable for it.
From the Scrum Guide: “The Product Goal is the long-term objective for the Scrum Team. They must fulfil (or abandon) one objective before taking on the next.”
Congratulations! You scored the pass mark of 85% or above!
Good try, but unfortunately, you did not score 85% or above.
Copyright © 2023 Red Tangerine. All Rights Reserved. See our privacy policy.