It’s a lot easier to estimate a story that’s small — which can lead to more accurate estimates, and better predictability.
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...
InfoQ article: "Pulling Power: A New Software Lifespan" - 0 views
-
how Kanban metaphor from Lean manufacturing and the Feature Injection template play into Behaviour Driven Development, working together to help us identify the most important software, reduce unnecessary artifacts at each stage of development, and produce the minimum necessary to achieve a vision
-
The artifacts signal each role to create further artifacts until the vision is implemented and the business value is earned
-
"Generating reports," he says, "is like lead. It's easy to work with, and it's cheap. It's also heavy, worthless, and drags you down. Developers sink a lot of time into writing report software. Why? Buy it, install it, hack it so it works. Use Excel. Don't spend money writing report software, unless you're the kind of company that sells them to other companies.
1 - 5 of 5
Showing 20▼ items per page