The Humanizing Work Guide to Splitting User Stories cover image

The Humanizing Work Guide to Splitting User Stories

The definitive guide to splitting features & stories, including the latest versions of Richard Lawrence's popular story splitting flowchart.

Profile image of Richard Lawrence
Oct 28, 2009 • 26 min read
5.00 (1)
Product Specifications
Product Increment
Vertical Story Slicing

Summary

The article outlines a definitive guide to splitting features & stories, including the latest versions of Richard Lawrence's popular story splitting flowchart. It gives us an in-depth understanding of user stories and why splitting them matters. Within the context, it details that splitting user stories into smaller valuable/manageable pieces allows teams to get high-quality feedback from the user's perspective. Read this guide to learn more about splitting user stories, attributes of good user stories, and how to compare them to vertical slides.

Takeaways

  • A good user story must contain this six key attributes. They should be: Independent, Negotiable, Valuable, Estimable, Small, and Testable.
  • A user story is simply a description of how the system will behave from the user's perspective.
  • Story splitting allows the team to get high-quality, valuable feedback on short intervals.

Suggested Resources