user-story-splitting

To split a large epic, apply systematic story splitting patterns like workflow steps, rule variations, and data variations to break it into smaller, independently deliverable user stories without losing user value.

For user stories with multiple When/Then acceptance criteria, use the acceptance-criteria complexity pattern to isolate each criterion into a separate, independently testable story while preserving the original epic's intent.

Break down oversized backlog items by applying an eight-pattern framework, including major effort milestones and external dependencies, to ensure each split story is small enough for estimation and single-sprint delivery.

Horizontal slicing and arbitrary chopping are anti-patterns because they produce stories that cannot be independently delivered or tested, reducing user value and complicating release sequencing.

Yes, use a validation checklist to ensure each split user story can be developed and tested independently, and that the resulting stories collectively add up to the original epic's scope.

Use the external dependencies pattern when a backlog item relies on third-party services or separate teams, splitting the story to isolate the dependent workflow for independent release and risk reduction.