What happens when the story is reviewed by the PO in the Sprint demo?

• A. The story is either accepted to the baseline or reworked
• B. The story is archived for future sprints
• C. The story is added to the release backlog automatically
• D. The story is split into two separate stories

Answer: (A)

The key idea is that at the Sprint Demo, the Product Owner validates what the team delivered against the agreed criteria and decides the next action. If the increment meets the acceptance criteria and is ready, the story is accepted into the baseline, meaning it becomes part of the current solution and is considered done. If it doesn’t meet the criteria, it’s not accepted and is sent back for rework, so the effort isn’t treated as finished until it fulfills the Definition of Done. This process keeps the team’s progress transparent to stakeholders and ensures only truly completed work is included in the baseline.

So, the story ends up either being accepted into the baseline or being reworked for future work. It isn’t archived automatically, nor added to the release backlog without review, nor typically split into two stories at the demo.