It’s a lot easier to estimate a story that’s small — which can lead to more accurate estimates, and better predictability.
The Daily Standup Wheel | AgileSparks - 0 views
daily standup wheel – AgileSparks - 0 views
Kanban development oversimplified: a simple explanation of how Kanban adds to the ever-... - 0 views
-
-
It’s easier to plan with smaller stories. With big stories — stories that might take weeks for a developer to implement — it becomes difficult to plan a development time-box — particularly when the iterations are only a couple of weeks. It seems that only a couple stories fit — and there’s often room for half a story — but how do you build half a story? Splitting them into smaller stories makes it easier to plan those time-boxes.
-
Shrinking stories forces earlier elaboration and decision-making. Where product owners could write their stories fairly generally and consider many of the details later, now breaking them down into smaller stories forces more thinking earlier in a planning lifecycle.
- ...36 more annotations...
1 - 5 of 5
Showing 20▼ items per page