This is a good post that talks about breaking down user stories. It talks about patterns that teams will typically follow to break down stories. It gives some good examples and explanations as to what is good and bad about these different patterns and discusses how they stack up to the INVEST criteria.
Most user stories are too big—at least, this is how it tends to be for teams making the transition to incremental development and delivery. After discussing the benefits of splitting stories into manageable increments, a team generally goes through (at least) these stages of development:
- splitting stories along process lines, then
- splitting stories along architectural lines, then
- splitting stories along procedural lines, then finally
- splitting stories into smaller stories
Read more here…