Backlog items need to be small enough so they can be delivered within a single Sprint. Sometimes, though, they’re just too big.
When items are too big to be delivered within a single Sprint, the team must slice the item into smaller pieces. SPIDR, by Mike Cohn, is a useful mnemonic to help teams work out ways to break large backlog items into smaller ones.
When the team doesn’t know how to slice a Backlog item into smaller pieces a “spike” is a useful activity.
Defining the steps a user takes can help a team slice large items into smaller pieces.
Split a large Product Backlog item by browser type, device type, or hardware, or by parts of a complex user interface (UI).
You may be able to deliver value in an iteration by focusing on one type of data.
Relaxing support for the rules in an iteration can make large stories smaller.