In Agile and Scrum frameworks, specifically during the Sprint Review and Sprint Retrospective, any work that does not meet the " Definition of Done " (DoD) cannot be considered complete or demonstrated to the customer.

Why Choice A is correct:

Maintaining the Backlog: According to the Scrum Guide, incomplete user stories are returned to the Product Backlog. They do not " automatically " move to the next sprint.

Reprioritization: The Product Owner must re-evaluate these stories. Business priorities may have shifted, or new information discovered during the sprint might make an incomplete story less valuable than other items currently sitting in the backlog.

Transparency: Moving them back ensures that the team’s velocity is calculated accurately (only counting completed points) and that the Product Owner maintains control over the project ' s direction.

Analysis of other options:

B (Remove these user stories): Just because a story wasn ' t finished in one sprint doesn ' t mean it lacks value. Removing them without a business justification violates the goal of delivering maximum value to the customer.

C (Advance to the top of the next sprint): This is a common mistake in practice, but it is technically incorrect according to Agile principles. The Product Owner, not a default rule, decides the priority of the next sprint. Forcing them to the top bypasses the Sprint Planning process.

D (Extend the sprint length): One of the core tenets of Scrum is the Timebox. Sprints have a fixed duration to create a predictable rhythm (cadence). Extending a sprint to finish work breaks this cadence and hides the team ' s true capacity/velocity issues.

Key Concept: The Project Management Institute (PMI) and the Agile Practice Guide emphasize that Incomplete Work (Choice A) should always be re-estimated and re-prioritized. This prevents " technical debt " from being hidden and ensures that the team is always working on the highest-priority items as defined by the most current business needs.