SAFe-Agilist Product Development Flow Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Because it makes it difficult for managers to track team progress.

  Why it's wrong here

  Management tracking is not the reason high utilization reduces performance. The issue is technical and related to queuing theory. High utilization leads to longer wait times, which is a physical reality of the system's throughput, regardless of whether managers are tracking the progress or not.

• ✓

  Because it eliminates the buffer needed to handle variability.

  Why this is correct

  High utilization leaves no room for error, variation, or urgent work. Without slack, the system becomes fragile. As soon as a delay occurs, it cascades through the pipeline because there is no spare capacity to absorb the impact, leading to severe delays and a breakdown in the flow of value.

• ✗

  Because teams are more likely to work on the wrong features.

  Why it's wrong here

  Utilization is about the volume of work, not the priority of it. High utilization might lead to teams finishing many things, but it does not inherently mean they are working on the wrong things. The issue is that the sheer volume of work prevents the system from flowing efficiently.

• ✗

  Because it discourages teams from using automated tools.

  Why it's wrong here

  There is no direct correlation between high utilization and the adoption of automation. In fact, teams might be highly utilized precisely because they have not automated manual steps. The problem is the lack of buffer capacity, which prevents the system from being adaptable and efficient during periods of high demand.