How can a scrum team best address frequent work being moved to the next sprint?

When a Scrum team frequently finds work being carried over to the next sprint, splitting stories into smaller units is an effective approach to address the issue. Large user stories, or "epics," can often become overwhelming and lead to work being incompletely finished at the end of a sprint. By breaking these larger stories into smaller, manageable tasks, the team can improve their ability to estimate what can be accomplished within a sprint. This practice aids in enhancing clarity and focus, enabling the team to deliver increments of value more consistently and with greater success.

Smaller units allow for more accurate planning and can lead to reduced uncertainty, as the team can better assess their capacity and velocity. It also enables more straightforward prioritization and may help reveal dependencies or challenges sooner, providing the team with valuable insights early in the sprint.

Increasing the sprint duration might provide more time to complete work, but it does not fundamentally address the underlying issue of scope and capacity. Assigning more resources to the team could lead to coordination challenges or complications without guarantee of efficiency. Holding daily stand-ups more often, while beneficial for communication, does not directly tackle the problem of uncompleted work from one sprint to the next. Thus, breaking down stories is a strategic solution that directly addresses the root cause