A Product Owner is reviewing the team's Iteration Burndown chart mid-iteration and sees that the remaining work line is flat for several days, even though the team reports they are working on multiple stories simultaneously. What is the most likely explanation and the best PO action?
A flat burndown while the team works on many stories simultaneously typically signals excessive WIP, which delays value delivery. The Product Owner should collaborate with the team to enforce WIP limits and encourage finishing work before pulling new items. This improves flow and makes progress visible on the burndown chart.
Why this answer
A flat Iteration Burndown chart during active work usually means stories are started but not completed, often due to excessive work in progress. The Product Owner should work with the team to limit WIP, encourage swarming, and focus on finishing stories to achieve a steady burndown. This aligns with SAFe's emphasis on flow and continuous delivery.
Exam trap
The trap here is attributing a flat burndown to estimation errors or external blockers rather than recognizing the internal symptom of too much work in progress.