What should the Development Team do if it realizes it has selected too much work during the Sprint?

The Development Team should remove some work or Product Backlog items with the Product Owner if it realizes that it has selected too much work during the Sprint. This approach is aligned with the principles of Scrum, where collaboration and communication between the Development Team and the Product Owner are essential for managing the Sprint Backlog effectively.

When the team acknowledges that it has overcommitted, it’s critical to assess the situation and prioritize the most valuable work that can realistically be completed within the Sprint timeframe. This ensures that the team can focus on delivering a potentially shippable increment of the product while maintaining a sustainable pace. Having a discussion with the Product Owner allows for informed decision-making about which items can be deprioritized without compromising the overall goals of the Sprint.

The other choices do not align with Scrum principles. Increasing the workload capacity would likely lead to overburdening the team and could result in decreased quality or burnout. Continuing with all selected items could compromise the team’s deliverables and lead to unfinished work, which counters the objective of producing a potentially shippable product increment. Postponing the Sprint is not a viable option in Scrum, as it undermines the iterative process and commitment to delivering value in each Sprint cycle.