Scrum PSK-I Practice Exam Questions & Answers

A Kanban board is primarily used for visualizing the Workflow and managing WIP Limits. This visualization helps Scrum Teams make the flow of work transparent, track progress, and manage bottlenecks effectively. Limiting WIP ensures a pull-based flow, where new tasks are only started when there is available capacity, preventing overburdening the team. Reference: The Kanban Guide for Scrum Teams.

Kanban for Scrum Teams maximizes value delivered by:

1. Enabling Tighter Empirical Feedback Loops via Faster Cycle Times (Option B):

Kanban practices help Scrum Teams reduce Cycle Times, which is the time it takes for a work item to move from 'start' to 'finish.' Faster Cycle Times mean that feedback on work done is received more quickly, allowing the team to make necessary adjustments sooner. This rapid feedback loop enhances the empirical process control central to Scrum, thus ensuring that the team is always delivering value in line with the needs of stakeholders(

2. Optimizing the Flow of Value (Option C):

Kanban focuses on optimizing the flow of work through the team's process. This is achieved by limiting Work in Progress (WIP) and actively managing flow metrics such as throughput and cycle time. By optimizing flow, teams can ensure that work items are completed efficiently and effectively, minimizing waste and maximizing the delivery of value to the customer(

The other options are less accurate:

* Option A: Minimizing time spent in meetings/events is not the primary goal of Kanban; rather, it is about optimizing flow and value delivery.

* Option D: Minimizing transaction costs is more related to Lean principles, but it does not directly address the value delivered as effectively as options B and C.

* Option E: Choosing higher-value items to deliver is part of prioritization, which is more related to Product Backlog management than to Kanban's specific practices

Work in Progress (WIP) Limits can be adjusted at any time as needed to optimize flow and improve the system's efficiency. The decision to adjust WIP limits is typically informed by the team's observations of flow metrics (e.g., Cycle Time, Throughput, and Work Item Age) or to address bottlenecks or inefficiencies.

Supporting Reasons:

Kanban's Flexibility:

Unlike rigid frameworks, Kanban allows for flexibility in changing WIP limits whenever necessary to adapt to evolving conditions.

Scrum Events:

Adjustments to WIP limits are often discussed during events like the Sprint Retrospective or Daily Scrum, but these are not the only times changes can be made.

Empirical Process Control:

Teams use transparency, inspection, and adaptation to decide when to change WIP limits based on real-time needs.

Why Not the Other Options?

B . When the Product Owner decides to change it:

Incorrect. WIP limits are a team decision and are not controlled solely by the Product Owner.

C . It never changes:

Incorrect. WIP limits are not static; they are dynamic and evolve based on team and system needs.

D . Only during the Sprint Retrospective:

Incorrect. While the Sprint Retrospective is a common time to discuss adjustments, changes are not restricted to this event.

E . Only during Sprint Planning:

Incorrect. Sprint Planning focuses on selecting work for the Sprint, not exclusively on adjusting WIP limits.

F . Only during the Daily Scrum:

Incorrect. Adjustments can be made during the Daily Scrum but are not limited to this event.

Adjusting WIP limits at any time ensures the team maintains an optimal flow, a core principle of The Kanban Guide for Scrum Teams.

Kanban emphasizes explicit policies for better transparency and alignment, and elements such as the Definition of Done, Definition of Ready, and Product Backlog refinement can be utilized as explicit policies to clarify the Scrum Team's working agreements. These policies help the team make consistent decisions and streamline their processes. Reference: The Kanban Guide for Scrum Teams and The Scrum Guide.

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.

Little's Law states:

* Average Cycle Time = Average Work in Progress (WIP) / Average Throughput.

Little's Law is used to understand and forecast the performance of a workflow system. It implies that if you know two of these three variables (Cycle Time, WIP, Throughput), you can calculate the third. The correct formula is Option A(

Options B, C, and D do not correctly state Little's Law.

Adjusting WIP limits can directly impact Cycle Time and overall flow by reducing bottlenecks and increasing focus. Lowering WIP can enhance the team's ability to complete work within a Sprint by minimizing task switching and promoting faster delivery of value. Reference: The Kanban Guide for Scrum Teams.