Limit Work in Progress (WIP)

Correct Answer: Through team experimentation and empirical data analysis

A mature Disciplined Agile team should determine WIP limits through experimentation and empirical data analysis. This approach aligns with core agile principles of inspection and adaptation, allowing teams to find their optimal flow based on real-world experience and results. Other approaches are incorrect because: Following industry standard recommendations fails to account for team-specific contexts, capabilities, and unique circumstances that affect workflow. Relying solely on capacity planning calculations and past sprint metrics is too rigid and may not reflect current team dynamics or evolving conditions. Implementing a fixed ratio per team member is overly prescriptive and does not consider work complexity, team maturity, or process variations. Each team needs to find its own optimal WIP limits based on their specific context and circumstances.

Correct Answer: Start with a reasonable WIP limit and adjust based on team feedback and performance

In Disciplined Agile, the best approach to implementing WIP limits is to start with a reasonable limit and then adjust based on team feedback and performance data. This approach aligns with DA's pragmatic, context-driven principles and allows teams to learn and adapt their processes. This method is superior because: - It embraces empirical process control - It allows teams to learn from experience - It supports continuous improvement - It recognizes that optimal WIP limits are team-specific The other options are problematic because: - Using velocity metrics and historical data for initial WIP limits is premature, as the team needs to establish baseline performance first - Setting WIP limits based on team size plus buffer is too rigid and doesn't account for work complexity or team dynamics - Using critical path method and resource allocation statistics is overly complex for initial implementation and doesn't align with agile principles of simplicity and adaptation

Correct Answer: It reduces context switching and improves flow efficiency

Limiting Work in Progress (WIP) is a key practice in Disciplined Agile that primarily focuses on reducing context switching and improving flow efficiency. This is the correct answer because: When teams limit their WIP: - They can focus on completing tasks before starting new ones - Mental context switching is reduced as team members focus on fewer items - Work flows more smoothly through the system - Quality improves due to increased focus - Cycle time decreases The other options are incorrect because: - Increasing team capacity and parallel work streams actually goes against the principle of WIP limits and can lead to reduced efficiency - Taking on additional work items while maintaining productivity is contradictory to the purpose of WIP limits - Maximizing resource utilization by keeping team members fully occupied creates overburden and reduces overall effectiveness