Story Splitting | Glossary

Definition:

In order to keep an Agile release cadence, features are required to be broken down into smaller stories. A story needs to be small enough that the development team can develop the feature. Story Splitting involves breaking up a large story into smaller ones with an objective that it can be completed in the iteration. 

Benefits:

  • If done well, user story help deliver the highest value
  • A proper splitted user story behaves as a building block of the product
  • Effective user stories reduces risk 

Further Reading:

  • ‘User Stories Applied’ by Mike Cohn
  • ‘Writing Effective User Stories’ by Thomas and Angela Hathway
  • ‘Introduction to User Stories’ by William Krebs

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.