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.

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 ​​.

Work in Progress (WIP) and Work Item Aging are considered leading indicator metrics in Scrum with Kanban. Leading indicators are metrics that provide information that can help predict future outcomes or performance.

• Work in Progress (WIP): This metric indicates the number of work items currently being worked on and can provide early signals about potential bottlenecks or issues in the workflow. Managing WIP effectively can help teams optimize their flow and predict how work might proceed in the future.

• Work Item Aging: This metric shows how long work items have been in progress without being completed. It provides an early indication of delays and can help teams identify items that might need attention to maintain a steady flow

When Developers add Kanban to Scrum, the way they use the Sprint Goal during their Daily Scrum can change. In traditional Scrum, the Sprint Goal is a shared commitment for the Sprint. However, in Professional Scrum with Kanban, the focus shifts to the flow of work and delivering value incrementally.

While the Sprint Goal still provides direction, the Daily Scrum may involve discussions about:

Progress towards the Sprint Goal: How are we progressing towards the overall goal?

Work in Progress (WIP): Are we adhering to WIP limits?

Blockers and impediments: What is preventing the team from progressing?

Prioritization: Are we working on the highest-value items?

By focusing on these aspects, the team can ensure that they are delivering value continuously and efficiently.

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 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. References: 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