Pass the Scrum Professional Scrum with Kanban PSK-I Questions and answers with ValidTests

While WIP is a crucial metric for Kanban teams, it is not a flow metric. Flow metrics measure the movement of work through the system, while WIP measures the amount of work currently in progress.

Here's a breakdown of the other options:

Cycle Time:The time it takes to complete a piece of work from start to finish.

Throughput:The rate at which work is completed.

Work item age:The amount of time a work item has spent in the system.

All of these metrics provide insights into the flow of work and can be used to identify bottlenecks and optimize the workflow.

Therefore, option B, "Work in Progress (WIP)," is the correct answer.

The primary effect of limiting Work in Progress (WIP) is to create a pull system. A pull system ensures that new work is only started when there is capacity, meaning that work is "pulled" into the system when the team has the availability to do so. This approach prevents overloading the team and helps maintain a steady and predictable flow of work, aligning with the Kanban practices within the Scrum framework

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.

An SLE combines a timeframe (elapsed days) and a probability, representing the likelihood that a work item will be completed within that timeframe. This helps to set realistic expectations for stakeholders and guide the team in maintaining a predictable flow. References: The Kanban Guide for Scrum Teams​.

A Service Level Expectation (SLE) in Kanban provides an agreement or expectation regarding the time it will take to complete a work item. An SLE consists of two main elements:

1.A probability (Option B): This is the likelihood or confidence level (e.g., 85%) that a work item will be completed within the specified period.

2.A period of elapsed days (Option D): This defines the maximum amount of time (e.g., 10 days) expected for a work item to be completed. The combination of these two elements helps set clear expectations and guide planning and forecasting efforts(

Options A (A cost of delay) and C (A forecasted date) are not part of the standard elements defining an SLE. The cost of delay is a concept related to prioritization, and a forecasted date is usually derived from the SLE but is not part of it.

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.

When Developers limit Work in Progress (WIP) within a Sprint:

1.Developers Stop Beginning Work and Start Finishing Work (Option A):

Limiting WIP encourages the team to focus on completing work that has already been started rather than starting new tasks. This "stop starting, start finishing" approach helps to reduce multitasking and ensures that tasks are completed more efficiently(

2.Self-management Strengthened Due to Increased Transparency (Option C):

Limiting WIP increases transparency by clearly showing what work is in progress and what remains to be done. This heightened visibility encourages the Developers to self-manage more effectively, as they can see what needs attention and make collective decisions about the next steps(

3.Increased Collaboration/Swarming Between Developers (Option D):

With a limited amount of work in progress, Developers are more likely to collaborate or "swarm" on the tasks that are currently active. This can lead to faster completion of tasks, shared knowledge among team members, and a stronger sense of teamwork(

Option B (The amount of work done by the end of the Sprint would be reduced) is not necessarily correct. Limiting WIP does not inherently reduce the amount of work completed; instead, it aims to improve focus, reduce waste, and ensure more consistent delivery.

While refining the Product Backlog is essential in Scrum, it is not an essential component specifically for achieving flow in Kanban practices. Achieving flow requires visualizing the workflow, limiting WIP, actively managing WIP, and continuously inspecting and adapting the workflow. Frequent Product Backlog refinement helps with the overall Scrum framework but is not directly tied to the initial goal of achieving flow in a Kanban system

Supplementing Scrum with Kanban practices encourages team collaboration and swarming. Kanban practices such as visualizing the workflow, limiting WIP, and focusing on flow metrics foster an environment where team members are more likely to collaborate closely to resolve bottlenecks and ensure a steady flow of work. This collaboration, often called "swarming," involves team members working together on fewer items to complete them faster, thereby enhancing team dynamics and efficiency

The essential flow metrics for Scrum Teams utilizing Kanban are:

Throughput: Measures the number of items completed within a time period.

Lead Time: Time from when an item enters the system to when it exits.

Cycle Time: Time it takes to complete a work item once it starts.

Work in Progress (WIP): The number of items currently in progress but not completed.

These metrics are foundational in understanding and optimizing flow within Kanban systems used alongside Scrum​​. "Work Item Age" and "Cumulative Flow Diagram (CFD)" are useful metrics but are not listed as primary flow metrics in Kanban for Scrum Teams.