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%.
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.
Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint. This does not mean that Scrum expects the team to be made up of cross-functional individuals.
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.
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:
As described in the Scrum Guide, “The Sprint Backlog is a plan by and for the Developers.”
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 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.
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:
The most important things to consider when discussing pulling in additional Product Backlog items into the Sprint is if doing so risks the Sprint Goal and the Increment. The Developers may also consider using the capacity in other useful ways, such as paying off some technical debt or using the time for self-learning, instead of always looking to pull the next item from the Product Backlog.
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.
Congratulations! You scored the pass mark of 85% or above!
Good try, but unfortunately, you did not score 85% or above.