A story too big for a sprint must be split, and the way you split matters. Each piece must still be valuable on its own: a thin slice through the whole system that a user could use, not a layer of it.
Common patterns:
- By workflow step: request a return, then print the label, then track it.
- By business rule: refunds under $100 first; manager approval for bigger ones later.
- By data or input variation: card refunds first, store credit later.
- By operation: create, view, change, cancel.
- Simple case first: the most common path now, the rare variations later.
The split to avoid is by layer: "build the screen", "build the database", "build the interface". None of those is usable alone, so none can be demonstrated or released, and the risk stays hidden until all are done.