The Professional Scrum with User Experience (PSU I) practice assessment is available to anyone who would like some help preparing for the official Scrum.org PSU 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 PSU 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:
With the caveat that the Scrum Team should still produce at least one Done Increment per Sprint.
The Scrum Master has an accountability to coach the Scrum Team on self-management within the boundaries of the Scrum framework. It is not up to the Scrum Master to design team makeup.
Scrum Teams should be cross-functional. Scrum does not recognise separate design and delivery Scrum teams. Dual Track Agile is about the Scrum Team moving as one unit and taking accountability for completing both discovery and delivery work.
Note that hypotheses statements state the outcomes and benefits that a user might get with a feature. Just because users desire a particular feature does not necessarily mean that developing it will lead to outcomes or value for either users or the business.
Product Backlog refinement is an ongoing activity by the Scrum Team which includes breaking large items down so they fit into the Sprint. Occasionally, some UX work may span more than one Sprint.
High value, high risk items should be experimented on first so that the Scrum Team can validate the hypothesised value and reduce the risk as soon as possible.
There is no such prescription.
The user experience should be a concern of everyone on the Scrum Team.
Decisions on design are best made based on empirical evidence.
The Product Owner is accountable for maximising value, how this is done may vary widely. The Product Owner should not act as a team proxy as this would reduce transparency, create a bottleneck on the Product Owner, and reduce the rest of the Scrum Team’s ability to understand stakeholder needs and thus come up with the best possible solutions.
Value may mean different things in different contexts. However, the only true way to know if something is valuable is to test its value proposition.
Congratulations! You scored the pass mark of 85% or above!
Good try, but unfortunately, you did not score 85% or above.