Definition

Before a user story is ready to be scheduled for implementation in an upcoming iteration, it should be "small enough," the usual rule of thumb being "a story that can be completed within the iteration". However, many user stories start out larger than that. "Splitting" consists of breaking up one user story into smaller ones, while preserving the property that each user story separately has measurable business value. What is Story Splitting?

释义

对于一个用户故事，在下一个迭代中应该准备好一个实现计划，用户故事应该"足够的小" ，通常定义其是否足够小的准则是“一个故事应该能够完成在一个迭代中”.然而，很多用户故事刚开始的时候都很大，并不是一个迭代就能开发完成的."Splitting"主要就是去分割用户故事使之足够的小，同时保留每个用户故事分别有可衡量的商业价值。