How would you break a large epic into sprint-ready user stories?

Why it exists

A large epic, build a shopping cart, describes an outcome, not a plan of work a team can start on Monday. Left as one block, it hides its risk until late and gives stakeholders nothing to look at until everything is done. Story splitting exists because teams need to ship in small, working increments to get feedback early, catch wrong assumptions cheaply, and keep a sprint's worth of work small enough to actually estimate.

The mental model

Slice the epic like a layer cake cut vertically, not horizontally. A horizontal slice takes one whole layer, all the database work, then all the API work, then all the UI work, and nobody can taste the cake until every layer is done. A vertical slice takes a thin wedge straight through every layer at once, a small piece of database, API, and UI together, so each story is a complete, demonstrable bite of the final product from day one.

How it works

Start with story mapping, lay out the user's journey step by step across the top, then stack variations and details underneath each step, which turns a vague epic into a visible backbone of small, ordered actions. Slice each step into an end to end story that touches every layer it needs to function on its own, then check it against INVEST, independent, negotiable, valuable, estimable, small, testable, and attach concrete acceptance criteria. Finally sequence the resulting stories by business value and risk, pulling forward whichever slice tests the riskiest assumption first.

When it matters

This decides outcomes whenever an epic spans multiple sprints or multiple engineers, since a horizontally sliced plan hides integration problems until the very last sprint, when there is no time left to fix them. The footgun is treating story splitting as pure task breakdown, cutting work by component, backend ticket, frontend ticket, database ticket, which produces stories nobody can demo individually and forces a big bang integration at the end regardless of how well each ticket was estimated.

A concrete example

For the epic build a shopping cart, a vertical breakdown looks like this. Story one, a shopper adds a single item to the cart from a product page. Story two, a shopper views a cart summary with item names and prices. Story three, a shopper updates an item's quantity. Story four, a shopper removes an item. Each ships independently, touches UI, API, and data together, and by story two stakeholders already have something real to click through, well before checkout exists.