user-story-splitting

To split large user stories for sprint planning, provide the original story with its acceptance criteria to apply eight splitting patterns, producing independently deliverable stories that are testable and shippable within a single sprint.

You should decompose an epic into smaller user stories during backlog refinement when stories are too large to estimate, contain multiple when/then acceptance criteria, or bundle multiple workflows and personas together.

The eight patterns for splitting user stories are workflow steps, business rule variations, data variations, acceptance criteria complexity, major effort, external dependencies, DevOps steps, and Tiny Acts of Discovery (TADs).

Yes, you can split user stories containing multiple personas and workflows by applying the systematic decomposition patterns to separate them into smaller stories that each deliver independent user value.

Yes, you need the original story in user story format with acceptance criteria to effectively split it, as the criteria are used to validate that each resulting split story is testable and delivers user value.

The best way to break down a checkout epic is applying splitting patterns to separate workflows like shipping entry, payment, and order confirmation into independently developable and validatable user stories.