3 ms·

splitting a story up into as many tiny pieces as possible Honestly I think that's the intended outcome from the business's perspective. The smaller the piece

splitting a story up into as many tiny pieces as possible Honestly I think that's the intended outcome from the business's perspective. The smaller the piece of work, the easier it is to assign a cost and a benefit to it, and the easier it is to hand off to another developer.

Groxx 7y ago
>... and the easier it is to hand off to another developer. I have never seen this work out in practice. And it's like a 1%-of-the-time thing anyway. On the flipside, I've seen quite a few hours wasted adding fake subdivisions to tasks, probably close to 30% of the time. Outside of small, known bug fixes or tech debt cleanup, it's rare for a thing to wholly fit within a sprint.