The Professional Scrum with Kanban (PSK I) practice assessment is available to anyone who would like some help preparing for the official Scrum.org PSK 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 PSK I assessment:
This practice assessment consists of 20 questions to be answered in 20 minutes, with a pass mark of 85%.
Little’s Law only shows us that there is a relation between WIP, Cycle Time and Throughput. You should not use it to calculate your WIP limits.
Select all that apply:
Throughput is a key metric to use in the Sprint Review to inspect the progress and forecast. Teams can also decide to take Cycle Time and Work in Progress into the Sprint Review, however they are not key for this event.
Though Scrum Teams can decide to make changes to their Definition of Workflow at any time, the recommendation is to do it as part of the Sprint Retrospective. The Definition of Workflow will have a material impact on how the Scrum Team performs. Restricting changes to the regular cadence provided by the Sprint Retrospective event will reduce complexity and improve focus, commitment and transparency.
Select all that apply:
Cycle Time, Throughput and Work in Progress are key metrics for the Sprint Retrospective. Teams can also decide to take Work Item Age into a Retrospective, though this is not a key metric for this event.
The Developers are accountable for managing, executing and monitoring the plan for the Sprint. This plan is made transparent in the Sprint Backlog.
Select all that apply:
The Sprint Goal is a mandatory element of Scrum. Whether adding Kanban practices or not, there are no prescribed rules that prohibit Scrum Teams from pulling items into the Sprint or releasing Increments during the Sprint. The Sprint Goal is the single objective for the Sprint.
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.
Select all that apply:
With Professional Scrum with Kanban, Sprint Planning has more inputs and historical measures may make it easier to create a forecast.
The Definition of Workflow may span beyond the Sprint. This could include what happens to Product Backlog items during refinement before they are pulled into a Sprint, and validation of value after they are Done for example.
Select all that apply:
As described in the Scrum Guide, “The Sprint Backlog is a plan by and for the Developers.”
Select all that apply:
Work in Progress and Work Item Age are the leading indicators.
The Scrum team can decide to change their WIP limits at any time, however because changes to the Definition of Workflow will have a material impact on how the Scrum Team performs, changes made during the regular cadence provided by the Sprint Retrospective event will reduce complexity and improve focus, commitment and transparency.
Select all that apply:
Work Item Age and Work in Progress are two of the four basic metrics that Scrum Teams with Kanban need to track. The other 2 that are missing from this list are Throughput and Cycle Time.
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:
None of the above, though metrics such as Work Item Age can be helpful in Sprint Planning, the key metric to help the Scrum Team plan for the Sprint is Throughput.
As explained in the Kanban Guide for Scrum Teams, the SLE consists of a range of elapsed days and a probability associated with that period.
Select all that apply:
As explained in the Kanban Guide for Scrum Teams, the minimum requirements for the visualisation of the workflow are; explicit policies about how work flows through each state, a definition of the work items, a definition of the workflow states that work items flow through from start to finish, policies for limiting Work in Progress, and defined points at which the Scrum Team considers work to have started and to have finished.
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.
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.