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:
Select all that apply:
The Scrum Team is actually less likely to work in silos.
Select all that apply:
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.
There is no such prescription.
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.
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.
Select all that apply:
The Product Backlog contains everything that is known to be needed to improve the product.
Scrum recognises no specialisms. Anybody that is committed to creating any aspect of a usable Increment each Sprint is considered to be a Developer, and attendance at the Daily Scrum by the Developers is mandatory.
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.
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.
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.
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.