The document discusses various options and variations for user interactions on a system, including: - Searching in different languages or with different date ranges and criteria - Creating policies with different review requirements - Payment options with PayPal, Stripe or check - Entering and uploading data in different formats - Getting search results at different speeds - Performing different account actions like signing up, editing settings, and deleting It also provides advice on splitting user stories that are too large, suggesting combining very small stories or dividing large ones based on components like the front end, business rules, backend, and database.

1. Variations in Data
User can search in English
User can search in Spanish
Workflow Steps
User can create a policy directly
User can create a policy to be held for legal review
Business Rule Variations
User can search for flights between 2 dates
User can search for flights for “any weekend
between now and December”
User can search for flights +/- 3 days between
December 15 and December 20
Major Effort
User can pay with Paypal
User can pay with Stripe integration
User can pay with online check
Simple/Complex
User can search for flights with a maximum
number of stops
User can search for flights with a maximum
number of stops
and departing from SAN OR JWI
Data Entry Methods
User can enter data in text field
User can upload CSV
Defer Performance
User can get results within 5 seconds
User can get results within 1 second
Operations (CRUD)
User can sign up for an account
User can edit account settings
User can delete account
If you have stories that are trivially small, I would recommend combining them into
a single “combo story” that falls below the 123 threshold.
Sometimes the user stories are too big and the team has trouble thinking
beyond “horizontal splitting” (front end, business rules, back end, database).
Here are some patterns for splitting stories:
HOW TO SPLIT STORIES
THAT ARE TOO BIG
www.payton-consulting.com
www.payton-consulting.com