Scaled Agile Framework (SAFe) Advanced Scrum Master Practice Exam

What are two significant problems caused by too much work in process (WIP)?

1. It hides bottlenecks in the workflow; It indicates team overcommitment

2. It shows that the overall system is inefficient; It increases lead time

3. It limits team communication; It hides bottlenecks in the workflow

4. It requires more resources; It decreases productivity

The correct answer is: It hides bottlenecks in the workflow; It indicates team overcommitment

The choice highlighting that having too much work in process (WIP) hides bottlenecks in the workflow and indicates team overcommitment accurately captures two significant problems associated with excessive WIP. When WIP levels are too high, it can obscure visibility into the actual performance of the workflow. Bottlenecks, which are points in the process where work gets stuck or slows down, can become masked when there is too much work in progress. Teams may not be able to easily identify where delays are happening because they are overwhelmed with numerous tasks. This lack of visibility can hinder effective troubleshooting and process improvement efforts. Additionally, excessive WIP tends to signal that a team may have committed to more work than they can realistically handle. This overcommitment can lead to stress, burnout, and ultimately affect the quality of the work produced. Teams may struggle to meet deadlines or deliverables, further exacerbating project challenges and reducing overall effectiveness. This perspective aligns with the principles of Lean and Agile methodologies, which advocate for minimizing WIP to enhance flow and efficiency in the system. Prioritizing manageable workloads helps teams maintain high-quality outputs and allows for better identification of workflow issues.