Limiting Work in Progress (WIP)

Correct Answer: Start with a baseline of 1.5 times the number of team members and adjust based on team flow

The optimal approach to determining WIP limits in Kanban starts with a baseline of 1.5 times the number of team members, followed by empirical adjustment based on team flow. This method is effective because: - It provides a reasonable starting point that accounts for team size - It allows for natural workflow variations - It enables empirical optimization based on actual team performance - It maintains flexibility while preventing overload The other approaches are problematic because: - Using total capacity multiplied by active sprints can lead to excessive WIP and reduced efficiency - Setting limits based on team members plus high-priority items fails to consider workflow dynamics and can cause bottlenecks - Using average velocity from past sprints to set fixed limits creates inflexibility and doesn't account for different work states having different processing needs The key is to start with a reasonable baseline and then adjust based on observable flow metrics and team feedback, which enables continuous improvement of the process.

Correct Answer: Through team consensus based on empirical data and sprint performance metrics

The best approach for adjusting WIP limits in a Disciplined Agile team is through team consensus based on empirical data and sprint performance metrics. This aligns with core agile principles of empiricism and self-organization. Here's why this is optimal: - It respects the team's autonomy and knowledge of their own capacity - It uses actual performance data rather than theoretical calculations - It allows for continuous improvement based on real observations - It promotes team ownership of process improvements Why other approaches are suboptimal: - Management directives contradict agile self-organization principles and may not reflect team realities - Mathematical formulas based purely on capacity or team size oversimplify the complexity of work management - Using story points and velocity alone doesn't account for work complexity, dependencies, and team dynamics WIP limits need to be flexible and adjusted based on team experience, performance data, and collaborative agreement to be truly effective.

Correct Answer: It helps reduce bottlenecks and improves flow efficiency

WIP limits are a key Lean-Agile practice that helps optimize flow in a team's process by: Correct answer explanation: - Limiting the amount of concurrent work items - Preventing overloading of team members - Helping identify bottlenecks quickly - Improving focus and quality - Reducing context switching - Increasing throughput and delivery speed Why other options are incorrect: - Having team members work on multiple tasks simultaneously decreases productivity due to context switching and divided attention - Increasing the number of tasks in the system creates more complexity and reduces efficiency - Starting more work items to meet deadlines leads to reduced quality, more defects, and actually slows down overall delivery The core principle is that limiting work in progress leads to better flow, higher quality, and faster delivery by preventing overload and maintaining focus.