User Stories are a common tool used by Agile Teams to capture the spirit of a requirement without too much detail. Sometimes User Stories are too large for the team to complete safely in one Sprint. In fact, I recommend that you split the Stories into small enough sections so that you’re completing 5-10 Stories per Sprint; it improves the flow and makes it easier to deliver complete chunks of value at the of the Sprint.
In my classes I frequently ask teams to present what they’ve learned to their peers. At UBC they took it one step further. The teams were challenged to summarize Richard Lawerence’s Story Splitting Flowchart:
They created a play, “Spike Sherman”. Our story opens with Diane preparing the original User Story, “Cong + Sherman”.
Clearly too large – so the team’s splitter, Jason, applied the patterns from the handout and broke the Story into its...http://feedproxy.google.com/~r/NotesFromAToolUser/~3/o9HidPph5I8/story-splitting-a-play-spike-sherman.htmlread more