5 ms·
Not true at all. Every increment is supposed to be shippable and better quality than the one before. So the chunks cannot be too small or you risk never shippin
by AstralStorm 8y ago
Not true at all. Every increment is supposed to be shippable and better quality than the one before. So the chunks cannot be too small or you risk never shipping by never shipping critical functionality that is hard to chunk, or instead you end up with long stretches where software does not work and is not testable.
This also ignores the fact that there are evolutionary dead ends and digging yourself out of such a hole is hard.
- com2kid 8y ago> or you risk never shipping by never shipping critical functionality that is hard to chunk, #ifdef is a thing and it solves this problem.:) For more modern teams, branches also work!
- speedplane 8y ago> you risk never shipping by never shipping critical functionality that is hard to chunk You don't have to be perfect at dividing up a big project, but you should at least try. Breaking down big pieces of functionality into smaller pieces is one of the core tenants of Agile. In fact, your approach has far more risk. By refusing to try to break things down into smaller units, you risk not shipping anything because every feature is deemed "critical".