When the workload exceeds the Development Team's capacity during Sprint Planning, what should the team do?

When the workload exceeds the Development Team's capacity during Sprint Planning, the most appropriate action is to remove or change selected Product Backlog items. This approach aligns with the principles of Scrum, particularly the focus on delivering a potentially shippable increment of value within the Sprint.

By adjusting the scope of work to fit the team's capacity, the Development Team can ensure they are not overcommitted and can focus on completing a set of items to a high standard within the Sprint. This practice also fosters a sustainable pace, preventing burnout and maintaining quality over quantity.

Making sure the selected items are realistic and achievable within the Sprint helps maintain the integrity of the Sprint goal and allows the team to deliver value consistently. This iterative process encourages collaboration and continuous improvement, as the team learns from each Sprint and adapts their planning for future Sprints.

Other options, such as increasing the team's size or informing stakeholders about the capacity issue, do not directly address the immediate challenge of workload management during Sprint Planning. Skipping a Sprint is contrary to Scrum principles and undermines the commitment to delivering increments of value regularly.