domains / families / business / user-story-splitting

user-story-splitting

separate

Break a large story or epic into smaller deliverable stories using proven split patterns. Use when backlog items are too big for estimation, sequencing, or independent release.

When to use

• Break down large user stories, epics, or features into smaller, independently deliverable stories using systematic splitting patterns. Use this to make work more manageable, reduce risk, enable faster feedback cycles, and maintain flow in…

When not to use

• Horizontal slicing into front-end and back-end stories
• Task decomposition
• Arbitrary chopping of stories
• Splitting stories that are already small and well-scoped
• Splitting when it creates dependencies that slow delivery
• Technical task breakdown

Skill page

Source