During Iteration Planning, the Product Owner (PO) introduces a new Story to the team. They cannot come to a consensus on the size of the new Story and ask the PO for more details. After a lot of discussion, multiple dependencies with other teams emerge, so the team decides to leave the Story in the Team Backlog and not commit. Is the scenario portraying an anti-pattern?

During Iteration Planning, the Product Owner (PO) introduces a new Story to the team. They cannot come to a consensus on the size of the new Story and ask the PO for more details. After a lot of discussion, multiple dependencies with other teams emerge, so the team decides to leave the Story in the Team Backlog and not commit. Is the scenario portraying an anti-pattern?
A . No; the team left the Story in the Team Backlog for further refinement with the PO
B. Yes; the PO should not be in the Iteration Planning meeting
C. Yes; the team identified multiple dependencies with other teams
D. No; the PO provided details on the Story

View Answer

Answer: A

Explanation:

No, In this scenario Story need to be refined further with the PO.