Patterns for Splitting User Stories

This post is from richardlawrence.info by Richard Lawrence

Good user stories follow Bill Wake’s INVEST model. They’re Independent, Negotiable, Valuable, Estimable, Small, and Testable. The small requirement drives us to split large stories. But the stories after splitting still have to follow the model.

Many new agile teams attempt to split stories by architectural layer: one story for the UI, another for the database, etc. This may satisfy small, but it fails at independent and valuable.

Over my years with agile, I’ve discovered nine patterns for splitting user stories into good, smaller stories.

Click  here to see the full post.

This entry was posted in Agile, Kanban, Scrum. Bookmark the permalink.