James is a Product Owner. It is day seven of the Iteration and his team tells him that they may miss their Iteration commitment. What should James do?

Question

Options

• ASupport adding an Innovation and Planning Iteration directly after the current Iteration
• BAgree to add a person from the System Team to complete the work
• CEnsure the Iteration backlog is accurately prioritized
• DSupport splitting a Story into a coding story and a testing story, and then moving the testing story

• A
  12% (5)
• B
  7% (3)
• C
  78% (32)
• D
  2% (1)

Explanation

When a team signals a potential miss mid-Iteration, the Product Owner's proper response is to ensure the Iteration Backlog is accurately prioritized so the most valuable work gets completed first - if anything must be dropped, it should be the lowest-priority items, not high-value ones. This is a core PO accountability in SAFe: you can't always control what gets done, but you control what gets done first.

Why the distractors are wrong:

• A is wrong because Innovation and Planning (IP) Iterations are fixed cadence events at the end of a PI, not a rescue mechanism to be inserted ad hoc.
• B is wrong because adding people mid-iteration typically slows the team down (Brooks' Law) and the System Team has its own PI commitments.
• D is wrong because splitting a Story into a "coding story" and a "testing story" and deferring the test violates SAFe's Definition of Done and creates hidden technical debt - stories must be tested and accepted within the same Iteration.

Memory tip: Think of the PO as a traffic controller, not a firefighter. When the team is overwhelmed, the PO doesn't add lanes or call in backup - they make sure traffic flows in the right order so the most important cars get through.

No community discussion yet for this question.