Epic breakdown template
Split an epic into features and then into small, estimable user stories the team can finish in a sprint.
Use this templateFree, opens in your browser. No sign-up.
What is an epic breakdown?
In agile teams, an epic is a piece of work too big to finish in one sprint, such as “self-serve checkout”. An epic breakdown splits it into features, then splits each feature into user stories small enough to estimate and finish within a sprint. It turns a vague goal into a backlog the team can plan, and shows how much work the epic really is.
The template breaks the example epic, self-serve checkout, into four features (cart, payment, confirmation and order history) and ten user stories with story points, from saving a cart for later to reordering in one click. Notes explain how it was split: by workflow step, every story shipping value on its own, nothing over 8 points, and 40 points in total, about two sprints.
What's on the board
- How we split it
- By workflow step: cart → pay → confirm · Each story ships value on its own · Nothing over 8 pts: split it again · Total: 40 pts ≈ 2 sprints
Also on the board
- Epic
- Features
- Stories · points
- Edit quantities · 3
- Feature: Cart
- Save cart for later · 5
- Apply promo code · 3
- Pay by card · 5
- Feature: Payment
- Pay by invoice · 8
- Epic: Self-serve checkout
- Retry a failed payment · 3
- Order confirmation page · 2
- Feature: Confirmation
- Confirmation email · 3
- List past orders · 3
- Feature: Order history
- Reorder in one click · 5
How to fill in the epic breakdown template
- Click Use this template. It opens in the Kelvo app as a new board, saved in your browser. Double-click any box to change its text.
- Name the epic as an outcome. Replace “Self-serve checkout” with your epic, phrased as what users will be able to do.
- Split it into features. Add a box for each feature. Splitting by workflow step (cart, pay, confirm) suits user flows; you can also split by user type, by data or by business rule.
- Write stories under each feature. Select a feature and press Tab to add a linked story. Write each one as something a user can do, and check that it delivers value on its own.
- Estimate, then split again. Add the points after each story. Anything over 8 points gets split again.
- Add up and plan. Total the points and divide by your team's velocity to estimate the number of sprints, then move the stories into your backlog.
When to use it
- Turning a roadmap item into backlog items before sprint planning
- Estimating how many sprints an epic will take
- Finding the smallest slice you could release first
When to skip it
- For work that already fits in a sprint: write the stories directly
- During early discovery, when you don't yet know which features the epic needs. Map the user journey first with a story map
Working on an agile board in Kelvo
- Add notes fast
- Press S for a sticky note in the middle of your view. A sticky is a box like any other: link it, recolour it, resize it.
- Move cards between columns
- Drag a sticky into another column; select several with a drag box to move them together.
Questions
What's the difference between an epic, a feature and a user story?
An epic is a large goal that takes several sprints. A feature is a distinct capability within it. A user story is a small part of a feature, written from the user's point of view, that the team can build and finish within one sprint.
How small should a user story be?
Small enough to finish within a sprint, ideally in a few days. Many teams set a ceiling, such as 8 story points, and split anything above it. The INVEST criteria help: independent, negotiable, valuable, estimable, small and testable.
What are good ways to split an epic?
By workflow step, by user role, by type of data, by business rule, by the happy path before the edge cases, or simple before complex (pay by card before pay by invoice). Avoid splitting by technical layer, such as front end and back end, because neither half delivers value alone.
Related templates
User story template
Write a story as who, what and why, with details, Given/When/Then acceptance criteria and an INVEST check.
Definition of Ready & Done
The checklists a story must pass before the team takes it, and before anyone calls it done.
Product backlog
A ranked backlog with type, estimate and readiness, plus backlog health and the next refinement session.
Sprint review
Run the sprint review: a timed agenda, planned vs done, what was demoed, stakeholder feedback and backlog changes.
User story map
The user's journey as a backbone of activities, tasks under each, and stories sliced into releases (MVP first).
RICE prioritization
Score features by Reach, Impact, Confidence and Effort to rank a backlog with numbers instead of opinions.