3 ms·
Not necessarily. The idea here is that the customer has an idea about what he wants, but has only a vague idea about what he actually _needs_, and no idea about
by pflenker 7y ago
Not necessarily. The idea here is that the customer has an idea about what he wants, but has only a vague idea about what he actually _needs_, and no idea about what is technologically possible.
Methods like XP embrace that by allowing requirements to change over time, to account for the customer accumulating more knowledge about all three areas.
- repolfx 7y agoBut you can nail those things down before coding begins, just through talking with them. You don't need to literally change the code completely every week - iterating a plan is much easier than iterating a codebase!
- afarrell 7y agoBut with 2 weeks of coding, you can save yourself an hour of planning.
- pflenker 7y agoNot necessarily, and it really depends on the customer and on the software. You feed the learnings from one iteration into the next - it's not intended to change the code completely every week, but to allow maximum flexibility in the backlog.