Story splitting is the practice of breaking large user stories into smaller, outcome-oriented pieces that teams can finish within a sprint. The key principle is to split vertically by value rather than horizontally by technical layer (UI, backend, database). A good split is outcome-oriented, delivers or creates value, fits within a sprint, is testable, and uses deliberate constraints. The SPIDR framework (Spike, Paths, Interfaces, Data, Rules) provides five approaches for finding useful splits. Teams should split stories roughly two sprints ahead during backlog refinement, and splitting should be a collaborative effort between Product Owners and developers. Warning signs of a splitting problem include stories carrying over between sprints, work sitting in progress all sprint, and sprint reviews with few completed items.
