Splitting User Stories

Why do we want to split user stories

How do you eat an elephant?

One bite at a time. :) this is a cheesy joke, but in real world, teams often have to work on user stories or features that are complex or huge, and it can feel like eating an elephant. These large user stories either cannot be completed in an iteration or a sprint, or they are really complex, and teams don’t know how to get started on the work. In these cases, teams can split these large or complex user story into multiple smaller user stories, and that’s what we are referring to splitting a user story.

Splitting the user story really optimizes and really focuses on the 20% of the work that’s highly valuable and helps do prioritize the stories that are not so valuable.

The idea and mindset here is some story done is way better than everything undone.