3 ms·

This is basically what we've come to. We don't force break down until 13. There are occasions where it's either (1) far easier to keep something as one, large p

• sverhagen 3y ago
  Even for a 5 I would encourage a discussion to see if it is worthwhile to be split up. Smaller stories lead to smaller code reviews, easier for the code reviewer, quicker updates in standup, no one falling behind. You can still decide to keep the occasional 5, but it's worth the discussion.
  • Falkon1313 3y ago
    That depends significantly on your team's measure of points. My team would never waste time trying to split a 5. But a 34, we would almost always try to split. 21s, we try to limit how many of them there are, but we're wary of splitting too much because splitting them up into, say, three separate 8s and then having to add a 13 to puzzle piece them all back together again isn't necessarily an improvement. But I think our points scale is quite different from what many other teams use. In any case, you have to be wary of splitting things too much (or not enough). If your 'bricks' are 8s, 13s, and 21s, then splitting a 5 is just making more work. But if your 'bricks' are 1s, 2s, and 3s, then splitting a 5 may well be a good idea.
    • SkyPuncher 3y ago
      It sounds like you're team has anchored around 13 as what we'd call our 5. Neither is right or wrong, just different.