5 Ways to Split User Stories: The SPIDR Method

Splitting user stories. It’s something I get asked about every day. I got asked so much, that I invented the SPIDR acronym to make it easy to remember the 5 simple, but powerful, ways to split user stories.

S is for Spike. That’s one you are probably all familiar with. A spike is a research activity that can give you the knowledge you need to split a complex story. An example might be a build vs. buy decision involving a new component.

P is for Path. If a user can do something in multiple ways, that’s a great area for splitting. An example might be paying via credit card or Apple Pay. One story could make it possible to pay by card, the next by Apple Pay.

I is for Interfaces: Splitting your story by browser, or hardware, or delivering a complex interface in iterations. An example might be delivering a version that only works in Chrome this iteration, and saving Safari for another iteration.

D is for Data. You may be able to deliver value in an iteration by simplifying or restricting the data that's supported. For example, don't allow negative bank balances in the first iteration. Add support for those with a different user story in the next iteration.

R is for Rules. Relaxing support for the rules in an iteration can make large stories smaller. We talk a bit about splitting stories in my upcoming webinar . I hope you’ll join us.