---
title: "Story Splitting: Split User Stories So Teams Can Finish"
url: https://daily.dev/posts/story-splitting-split-user-stories-so-teams-can-finish-elu68dtmt
source_url: https://www.mountaingoatsoftware.com/blog/story-splitting-how-to-split-user-stories-so-teams-can-finish
type: article
source: "The Mountain Goat Software"
published: 2026-05-19T14:25:39.447Z
updated: 2026-05-19T14:26:03.471Z
tags: ["agile", "scrum"]
reading_time: 15
upvotes: 0
comments: 0
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Story Splitting: Split User Stories So Teams Can Finish

**[The Mountain Goat Software](https://daily.dev/sources/mountaingoatsoftware)** · 15 min read · 0 upvotes · 0 comments

## Summary

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.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.mountaingoatsoftware.com/blog/story-splitting-how-to-split-user-stories-so-teams-can-finish>

## Similar posts on daily.dev

- [The one thing every experienced engineer gets wrong](https://daily.dev/posts/the-one-thing-every-experienced-engineer-gets-wrong-qx6sxnvvh) · swizec.com · 34 upvotes · 5 comments
- [The "Negative split" software engineering effect](https://daily.dev/posts/the-negative-split-software-engineering-effect-k3nsworvo) · Manager.dev · 81 upvotes · 0 comments

---

Tags: [#agile](https://daily.dev/tags/agile), [#scrum](https://daily.dev/tags/scrum)

[View this post on daily.dev](https://daily.dev/posts/story-splitting-split-user-stories-so-teams-can-finish-elu68dtmt)