2 ms·
that sounds more like a symptom of forgetting to include refactoring in your agile loop, than an inherent issue with small iterations.
by beaconstudios 10y ago
that sounds more like a symptom of forgetting to include refactoring in your agile loop, than an inherent issue with small iterations.
- d--b 10y agoYes, in this tiny example, it could be avoided by adding a simple refactor in your second iteration. In general though, the customer may ask you some iteration that he doesn't realize imply a complete rewrite of the code. Like: "now I want the same thing, but I want it available 24/7 with no downtime". Or "Now we have a great text editor, we want to add live collaboration". "You know what would be great: that we could see what changed between 2 versions of the spreadsheet".
- beaconstudios 10y agotrue, and it's hard to work around unreasonable customer requirements. In the ideal circumstance you would have that conversation and explain that having 100% uptime guaranteed is basically impossible and aiming for e.g. 6-sigma uptime requires high ongoing costs - but I'm sure we've all experienced that "I can have it both ways" attitude.