The Professional Scrum Master (PSM I) practice assessment is available to anyone who would like some help preparing for the official Scrum.org PSM 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 PSM I assessment:
This practice assessment consists of 20 questions to be answered in 20 minutes, with a pass mark of 85%.
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.
The Scrum Framework is immutable, while implementing parts of Scrum is possible, the result is not Scrum. Dropping Scrum events results in lost opportunities for inspection and adaptation and reduces transparency.
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.
Select all that apply:
Scrum is a lightweight framework with various processes, techniques and methods that can be employed within the framework, such as the use of user stories and story points.
The Sprint Planning event is timeboxed to a maximum of 8 hours, regardless of Sprint length.
Once the Scrum Team determines that a Product Backlog item can be completed within one Sprint, it is deemed to be ready for selection. There is no “definition of ready” artifact or element in Scrum.
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 a lightweight framework that helps to generate value through adaptive solutions for complex problems. It does not provide guidance in designing the organisational structure.
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.
The Developers are accountable for managing, executing and monitoring the plan for the Sprint. This plan is made transparent in the Sprint Backlog.
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.
Scrum is a lightweight framework, on top of which complimentary practices can be added. Technical practices are not mandatory, but they could be a great benefit.
Defects are not just bugs in the product. A defect is anything that reduces the value of the product to a customer, user, or to the organization itself. Defects are generally things that don’t work as intended.
During the Sprint, scope may be negotiated between the Developers and Product Owner as more is learned.
Congratulations! You scored the pass mark of 85% or above!
Good try, but unfortunately, you did not score 85% or above.