POPM Iteration Execution Practice Question
During Iteration Execution, a Product Owner notices that the team's cumulative flow diagram shows the 'In Progress' column growing steadily while 'Done' remains flat. The team insists they are working hard. What is the most likely issue, and what should the PO do first?
⚠ Common exam trap
The trap here is assuming that a flat 'Done' column means the team is lazy or over-committed, rather than recognizing it as a symptom of work items that are too large to finish.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Work items are too large; the PO should facilitate splitting stories into smaller, independently deliverable slices.
A cumulative flow diagram with a widening 'In Progress' band and flat 'Done' indicates that work is starting but not finishing, a classic sign of stories that are too large or have hidden dependencies. The Product Owner should first help the team break down work into smaller, independently deliverable pieces so they can complete items within the iteration, improving flow and reducing WIP.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The team is over-committed; the PO should remove a feature from the Iteration Backlog.
Why it's wrong here
Over-commitment would typically show a large 'To Do' column and slow progress across all columns, not a growing 'In Progress' with flat 'Done'. Removing work without understanding the bottleneck could mask the real problem. The PO should first investigate why work is not flowing to completion, not simply cut scope.
- ✓
Work items are too large; the PO should facilitate splitting stories into smaller, independently deliverable slices.
Why this is correct
A growing 'In Progress' with flat 'Done' indicates work is starting but not finishing, often due to large stories that exceed the team's ability to complete in a short time. The PO should help the team slice stories into smaller vertical increments so they can be finished within the iteration, improving flow and reducing WIP.
- ✗
The Definition of Done is too strict; the PO should relax it to allow more items to be marked done.
Why it's wrong here
Relaxing the Definition of Done undermines quality and does not solve the underlying flow issue. A flat 'Done' column with rising 'In Progress' suggests work is not reaching the done state, which could be due to size or dependencies, not an overly strict DoD. The PO should not compromise quality to improve metrics.
- ✗
The team lacks technical skills; the PO should arrange training during the iteration.
Why it's wrong here
Skill gaps might cause slower progress, but the cumulative flow pattern specifically points to work not completing, not necessarily to a lack of skills. Training is a longer-term action and does not address the immediate flow problem. The PO should first examine work item size and WIP limits before assuming a skill deficiency.
About these practice questions
Courseiva writes every POPM question from scratch — 336 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Scaled Agile exam blueprint
This POPM practice question is part of Courseiva's free Scaled Agile certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the POPM exam.