methodatlas
Agile

Story Splitting

Turns backlog, sprint work, and team flow into a tangible result by identifying oversized stories, finding the smallest value slice, and reprioritizing.

Core question
How can the story be split into 2-5 slices, each delivering value or learning, without losing overall benefit?
MediumWorkshop + async30-60 min
Purpose

The method helps clarify backlog, sprint work, and team flow concretely. It sorts work by value, risk, and deliverability. The outcome is captured as smaller stories, acceptance criteria, and split rationale.

How it works

The team follows the steps: identify oversized stories, find the smallest value slice, split by path, rule, or scenario, check testability, and reprioritize. Each step is captured visibly. At the end, smaller stories, acceptance criteria, and split rationale are available so decisions, tests, or actions can follow directly.

Visual orientation

Method sketch for a quick mental model.

Story Splitting · Vertical Value SlicesCut an overly large story into small usable slices along workflow, data, rules, or roles
Story SplittingThe visual shows one large story, possible split axes, and several small vertical value slices.Split large stories into small usable slicesGood splits each deliver value and avoid purely technical horizontal layers.slice verticallyprioritizesplit axes helpLarge storyAs a user, I want to manage ordersWorkflowSearch → View → ChangeDataactive orders onlyRulessimple cases firstSlice 1view orderSlice 2change statusSlice 3check cancellationSequencerisk and value determine the nextslice

Flow

  1. 1Identify oversized stories
  2. 2Find the smallest value slice
  3. 3Split by path, rule, or scenario
  4. 4Check testability
  5. 5Reprioritize

The runsheet guides execution with 4 phases, timeboxes, 5 pitfalls, and clear stop criteria.

Open runsheet

Ideal for

  • Backlog Refinement
  • Sprint Planning
  • Incremental Delivery

Not good for

  • Architecture-only work
  • Fixed-scope contract items

Deep dive

In detail

Story Splitting follows a clear working logic: identify oversized stories, find the smallest value slice, split by path, rule, or scenario, check testability, and reprioritize. This turns the method into a visible thinking process rather than only a conversation. Participants move step by step from raw material, observations, or options toward a shared structure. As a result, smaller stories, acceptance criteria, and split rationale support decisions, learning, or further planning.

Facilitation

Prepare a clear guiding question, the right information, and a visible workspace. Plan about 30-60 min with 2-6 people and use the format in a workshop or asynchronously. The method needs clear structure and preparation; short timeboxes, visible intermediate results, and a parking lot for open questions help.

Output artifacts
Smaller StoriesAcceptance CriteriaSplit Rationale
Tags
Artifact templates
Story Splitting Working TemplateCompact working template for Story Splitting with context, input, output artifacts, and next step.
checklist

story-splitting-working-template.md

Compact working template for Story Splitting with context, input, output artifacts, and next step.

Story Splitting Checklist

  • Goal and context clarified
  • Input material gathered
  • Participants and roles named
  • Execution prepared according to the runsheet
  • Output artifacts created
  • Smaller Stories updated
  • Acceptance Criteria updated
  • Split Rationale updated
  • Open questions documented
  • Next step set with owner and date

When to choose differently

Short decision aid for existing alternatives.

Example Mapping

Statt Story Splitting, wenn ihr konkrete Beispiele als Brücke zwischen Fachsprache und Akzeptanzkriterien nutzen wollt.

Similar methods

All methods