POPM Iteration Execution 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.

• ✓

  The team is working on large stories that are not broken down; the Product Owner should help the team split stories into smaller slices.

  Why this is correct

  A flat line followed by a steep drop typically indicates that the team was working on large stories that could not be completed until late in the iteration. This creates a 'waterfall' pattern within the iteration. The Product Owner should collaborate with the team to split stories into smaller, vertically sliced items that can be completed in a few days, improving flow and providing earlier feedback.

• ✗

  The team is experiencing external dependencies; the Product Owner should escalate to the Release Train Engineer.

  Why it's wrong here

  External dependencies can cause delays, but they typically result in a burndown that stalls and then may never recover. The specific pattern of a flat line followed by a steep drop is more characteristic of large stories being completed late. While escalating dependencies is important, it does not directly address the observed burndown pattern. The Product Owner should first investigate story size and flow before escalating.

• ✗

  The team is over-committed; the Product Owner should reduce the number of stories in the next iteration.

  Why it's wrong here

  Over-commitment usually results in a burndown that never reaches zero, not a flat line followed by a steep drop. The pattern described suggests delayed completion rather than too much work. Reducing the number of stories might help, but it does not address the root cause of large stories. The Product Owner should first focus on improving story slicing to enhance flow and predictability.

• ✗

  The team is not updating their tasks; the Product Owner should remind them to update the board daily.

  Why it's wrong here

  While lack of updates can cause a flat line, a steep drop after three days often indicates that work was completed but not reflected until later. However, the more likely cause is that stories were too large and not broken down, leading to a delay in completion. Simply reminding the team to update the board may not address the underlying issue of story size and flow, so this is not the best first action.