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.

• ✗

  Eliminating all planning and working on items as they arrive.

  Why it's wrong here

  Eliminating planning creates chaos and makes it impossible to align the ART toward a common goal. SAFe requires cadence-based planning to coordinate efforts. The goal is to build resilience into the plan, not to abandon the planning process entirely in favor of a purely reactive, unpredictable mode of operation.

• ✓

  Using capacity buffers to manage surges in work demand.

  Why this is correct

  Capacity buffers provide a cushion against the inherent variability in arrival rates. By not planning 100% of their capacity, teams can handle unexpected urgent requests without derailing their primary commitments. This is a foundational flow strategy to ensure that the ART can remain stable despite fluctuating demands for work.

• ✗

  Requiring all stakeholders to submit requests six months in advance.

  Why it's wrong here

  Long lead-time requirements are rigid and do not accommodate the need for agility. They create massive backlogs that become obsolete before they are reached. This approach ignores the reality of dynamic markets and prevents the ART from being responsive to feedback or changing needs, which undermines the core agility objective.

• ✗

  Increasing the size of every team on the train.

  Why it's wrong here

  Increasing team size usually creates more overhead, communication complexity, and coordination challenges. It does not address the fundamental issue of arrival variability. Managing variability should be handled through systemic practices like buffering or better prioritization, not by simply throwing more people at the problem, which often decreases team productivity.