All glossary terms
Plan
Story splitting
Story splitting breaks a large user story into smaller stories that each independently deliver value. The smaller the stories, the smoother the flow, and the easier they are to estimate, review, and ship.
Richard Lawrence's splitting patterns are the canonical guide: by workflow step, by data variation, by interface, by happy-path-vs-edge-case, by major effort. A useful test: if a story is going to take more than 2-3 days for one engineer, split it. Splitting often surfaces hidden complexity, a 13-point story that 'feels' simple usually contains 2-3 stories the team didn't see until they tried to split it.