<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>story splitting on Agile Software Development</title>
    <link>https://agilesoftdev.com/tags/story-splitting/</link>
    <description>Recent content in story splitting on Agile Software Development</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://agilesoftdev.com/tags/story-splitting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Splitting User Stories Is a Skill Most Teams Develop Too Late</title>
      <link>https://agilesoftdev.com/splitting-user-stories-is-a-skill-most-teams-develop-too-late/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://agilesoftdev.com/splitting-user-stories-is-a-skill-most-teams-develop-too-late/</guid>
      <description>The large story is one of the most reliable predictors of sprint failure. A story that spans more than half a sprint occupies the team&amp;rsquo;s attention, resists review, and tends to arrive at the sprint boundary in a state of near-done that creates exactly the kind of work-in-progress debt that sprints are designed to prevent. Teams know this. They continue to carry large stories because splitting them well is genuinely difficult and the techniques for doing it are not intuitive.</description>
    </item>
    
  </channel>
</rss>
