User Story Splitting

If you work in an agile team, chances are you are using user stories to capture the customer’s needs. But I bet it often still takes too long to release valuable new features. This is risky, as you postpone critical user feedback.

During the retrospective, the team keeps highlighting that the user stories had dependencies. The user story was too big to fit in the sprint to begin with; it was impossible to give an accurate estimate because essential information was missing. On the other hand, the product owner signals that some user stories hold too much waste.

We all love user stories, but they don’t solve all the problems mentioned above. We must find ways to create more value by building less. A proven way is to apply story-splitting patterns. These patterns will split a user story into two or more new user stories that can be estimated, detailed, and build independently.

In this course, we present 7 story splitting patterns to get you on the way!

Let those big user stories come. From now on, we’ll split them into pieces.