Scrum PSK-I Practice Exam Questions & Answers

When WIP limits are implemented, Developers are encouraged to focus on completing existing tasks rather than starting new ones. This leads to a more collaborative approach, as team members may swarm to complete items together. Additionally, limiting WIP enhances transparency in the process, which in turn strengthens self-management by the team. These principles align with Kanban's emphasis on active management and the Scrum framework's focus on collaboration. Reference: The Kanban Guide for Scrum Teams.

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.

The Definition of Workflow includes the agreed-upon points at which the Scrum Team considers work to have started and finished. These points are determined based on the boundaries and scope of the team's workflow. This definition must be clearly understood by the entire team to track Work in Progress (WIP) effectively and manage flow efficiently. It is up to the Scrum Team to define these boundaries to suit their specific context and workflow needs.

A Cycle Time Scatterplot is a visualization tool used to display the cycle times for individual work items over time. This scatterplot provides several types of qualitative information:

1. General Cycle Time Trends (Option A): The scatterplot can show general trends over time, such as whether the cycle times are decreasing, increasing, or staying stable. This helps teams understand the overall direction in which their workflow efficiency is moving.

2. Single Cycle Time Outliers (Option B): The scatterplot also helps identify individual outliers --- work items that took significantly longer or shorter than usual to complete. These outliers can be further investigated to understand why they occurred and to prevent similar situations in the future.

3. Clusters of Cycle Time Outliers (Option C): In addition to single outliers, the scatterplot may reveal clusters of outliers. These clusters can indicate systemic issues, such as bottlenecks or recurring problems in a specific part of the process.

Since a Cycle Time Scatterplot provides all these types of information (general trends, single outliers, and clusters of outliers), the correct answer is D.

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.