PSK-I Exam Dumps - Professional Scrum with Kanban (PSK 1) Exam

Throughput, which measures the number of items completed over a specific period, is essential for forecasting future delivery rates. By analyzing historical throughput data, Scrum Teams using Kanban can make informed predictions about how many items they can complete by a given date. References: The Kanban Guide for Scrum Teams​​.

Kanban does not eliminate the need for a Scrum Master when used with Scrum. The Scrum Master remains an essential role to facilitate the Scrum framework, help the team adopt both Scrum and Kanban practices effectively, and ensure the team understands and adheres to Scrum principles.

The role of the Scrum Master includes coaching the team on both Scrum and Kanban practices, removing impediments, and promoting continuous improvement. Therefore, even when Scrum is used with Kanban, the Scrum Master is not optional but a critical role in ensuring that the integration of these practices is successful(

During Sprint Planning, the most relevant metric to consider is Throughput (Option B), which measures the number of work items completed in a given time frame (e.g., per Sprint). By reviewing past throughput, the team can make informed decisions about how much work they are likely to complete in the upcoming Sprint, taking into account their capacity and any potential changes in team composition or external factors.

•Service Level Expectation (A) is less relevant as it is more about setting expectations with stakeholders rather than planning the Sprint.

•Work Item Aging (C) is a leading indicator metric used to track how long current work items have been in progress, which is less helpful during planning.

•Work in Progress (D) indicates the current workload but does not provide historical data useful for forecasting in Sprint Planning

1.WIP Limits provide a boundary/container in which the Scrum Team self-manages (Option B):

WIP Limits establish clear boundaries within which the Scrum Team can make decisions about how much work they take on. This framework allows the team to self-manage their workflow more effectively, as they must decide collectively how to stay within these limits while delivering value.

2.As part of self-managing, Scrum Teams figure out their own WIP Limits (Option D):

A fundamental principle of Scrum is self-management. The team collectively decides its WIP limits, adjusting them based on empirical evidence and ongoing learning about their capacity, flow, and delivery capabilities. This decision-making process is a key aspect of the team's autonomy and self-management(

Options A and C are incorrect because WIP limits do not inhibit self-management (A); instead, they enable it. Additionally, a Scrum Master does not define WIP limits (C); the Scrum Team decides them.

The Kanban Guide for Scrum Teams outlines four primary Kanban practices essential for Scrum Teams:

Visualization of the Workflow.

Limiting Work in Progress (WIP).

Active management of work items in progress.

Explicit policies for workflow management, often including the identification of bottlenecks​.

Inspecting and adapting the workflow is not explicitly listed as a Kanban practice for Scrum Teams. While inspection and adaptation are fundamental to Scrum (due to its reliance on empiricism), they are not specific to the set of Kanban practices integrated into Scrum​​.