Kanban

Correct Answer: To calculate average completion time using WIP and throughput

Little's Law is a fundamental principle in Kanban systems that establishes the relationship between three key metrics: Work in Progress (WIP), Throughput, and Lead Time (average completion time). The formula states that Lead Time = WIP/Throughput, which helps teams calculate and predict the average time it takes to complete work items based on their current WIP limits and throughput rates. The other options are incorrect because: - Team member optimization is not related to Little's Law, as it focuses on work items rather than personnel - Task complexity and delivery speed correlation is not what Little's Law measures - Team velocity and customer satisfaction are different metrics that fall outside the scope of Little's Law's mathematical relationship between WIP, throughput, and lead time

Correct Answer: It marks when a work item is formally accepted into the workflow

The Kanban Commitment Point is a crucial concept that marks the moment when a team formally accepts a work item into their active workflow. This is the correct answer because: It represents the clear boundary between work being considered and work being actively pursued. At this point, there is a mutual understanding between the team and stakeholders that the item will be completed. The other options are incorrect because: Final approval occurs at the end of the workflow, not at the commitment point. Resource allocation happens throughout the workflow and isn't specifically tied to the commitment point. Prioritization typically occurs before the commitment point, during backlog refinement and planning activities. While prioritization influences which items reach the commitment point, it isn't the purpose of the commitment point itself. The commitment point serves as a clear signal that the team is taking responsibility for delivering the work item through their workflow system.

Correct Answer: Create a dedicated swim lane for urgent items with a separate WIP limit

Creating a dedicated swim lane for urgent items with a separate WIP limit is the most effective approach for handling expedited requests in Kanban because: - It maintains system predictability while accommodating urgent work - It provides clear visibility of expedited items - It prevents disruption to regular workflow - It helps track and limit the amount of urgent work in progress - It enables teams to manage expectations for both standard and expedited work Other approaches are less effective because: Adding extra columns creates unnecessary complexity and doesn't address the flow of urgent work. Moving urgent items to the front of queues disrupts flow, creates unpredictability, and can lead to constantly shifting priorities. Increasing WIP limits temporarily undermines the core Kanban principle of controlling work in progress, leading to reduced efficiency and potential bottlenecks.