End of Iteration
During an iteration, a team discovers that they cannot complete a story, what should happen next?
Pick ONE Option
- Review and improve the story for as long as needed until it is at a point where the team can complete it during that iteration
- Table the story until it can be groomed to a point where it can be decomposed or consumed by the team within an iteration
- Complete and demonstrate any parts of the story they are able to
- Defer the story for a future date
Why do you think those are the only options?
If the "iteration" you mention is a Sprint, who was present at Sprint Planning to make the initial forecast of work for meeting the Sprint Goal, and now ought to revise that forecast accordingly?
Where did these options come from? Did you invent them or did they come from a sample exam or other published resource? These options may reflect valid choices for an organization, but none are consistent with the Scrum Guide.
If a team cannot complete a particular story, or in Scrum's terms, Product Backlog Item, the first step would be to determine the impact on the Sprint Goal. Does not completing this particular Product Backlog Item mean that the Sprint Goal is in jeopardy? If the Sprint Goal is not in jeopardy, the work can remain unfinished and go onto the Product Backlog for consideration in the future. However, if the Sprint Goal is in jeopardy, the Developers and Product Owner may need to work together to plan a course of action to maximize the value delivered by the end of the Sprint.
There are 2 options missing.
- None of the first 4 listed
- Ask the Scrum Team how this specific instance should be handled
If you got these from a practice exam, I'd be very cautious using it to gain knowledge. The question and answers do not show an understanding of the Scrum framework.
All of the options have merit but I can't pick one without more context as to why the PBI can't be complete.