What happens to the tasks in a Sprint Backlog?

The tasks in a Sprint Backlog are specifically designed to be completed within the current Sprint. The Sprint Backlog is a subset of the product backlog that the team commits to delivering during the Sprint, which usually spans two to four weeks. The team selects items from the product backlog that they believe they can complete within this timeframe.

As the Sprint progresses, the team works collaboratively to accomplish the tasks outlined in the Sprint Backlog. This focus on completing tasks within the designated Sprint helps ensure that the team delivers potentially shippable increments of the product at the end of each Sprint. It also facilitates regular inspection and adaptation of the work being done, allowing teams to adjust their processes and improve their productivity over time.

The other options do not accurately describe the purpose of the Sprint Backlog. Discarding tasks after the Sprint contradicts the principle of delivering incrementally. Similarly, tasks intended for future Sprints belong in the product backlog, not the Sprint Backlog, and customer requests should be handled separately from the team’s focused work within the Sprint.