Differences

This shows you the differences between two versions of the page.

--- how_do_we_split_user_stories [2020/06/02 14:21] – external edit 127.0.0.1
+++ how_do_we_split_user_stories [2020/06/04 07:43] – [Need To Know More?] Changed Need to Want hans
@@ Line 1: / Line 1: @@
 ====== How Do We Split a User Story? ======
-Basic answer is "By end user value - ask yourself 'What kind of feedback do you expect from the customer at the Sprint Review.'"
+> Basic answer is "By end user value - ask yourself 'What kind of feedback do you expect from the customer at the Sprint Review.'"
-====== Premise ======
 User stories have a life-cycle. When we start into a release planning process, we might only have a "top 10" list of features required for this release. These are typically called Epics. Scrum Teams are told that they have to complete an entire user story before moving on to the next one in a Sprint and further that they should have between say 5-10 user stories per sprint. How do we get from the Epic to User Stories of this size? The answer is that we increasingly detail the requirements by splitting the Epic and subsequent User Stories into smaller and smaller User Stories.
@@ Line 28: / Line 25: @@
 To make sure you have something valuable ask yourself "Will the Customer be able to provide feedback on this functionality at the Sprint Review?" If you cannot figure out what kind of feedback the customer will provide, you probably have a user story that is more technical than from the business value that is being provided.
-====== Need To Know More? ======
+====== Want to Know More? ======
   * [[http://www.agileforall.com/wp-content/uploads/2012/01/Story-Splitting-Flowchart.pdf|Splitting Story Flowchart]] - An excellent reference for patterns for splitting stories.
@@ Line 36: / Line 33: @@
-~~LINKBACK~~
-~~DISCUSSION~~