4 ms·
6 months defines the ultimate release date. What we are planning is having a product ready in less than 5 with almost all major features and to add as much as w
by diegoperini 11y ago
6 months defines the ultimate release date. What we are planning is having a product ready in less than 5 with almost all major features and to add as much as we can (without rushing and breaking everything) until the release date.
The good thing is, almost all major features are the ones the team already had previous experiences before. We depend on a good analysis and our experience to be honest.
- madaxe_again 11y agoSo - if you've got past experience of these features, and can therefore estimate your time and resource need well, and know what major features are Must have (MoSCoW is your friend), this in my mind strengthens the case for waterfall - as you can accurately (enough) plan out a sane project plan which includes your must haves and has slots for your Should and Coulds which can get pushed out in contingency, and you can then run the whole thing with predictability, predictable budgets, predictable feature sets, and not end up caught short in a mad sprint cycle at the end. Agile is great if you've got a weak scope, or an unlimited budget, or all the time in the world - but in the scenario you describe, waterfall would be the model I'd apply.
- diegoperini 11y agoWhat if the product, once released, will keep being improved with continuous development for at least 2-3 years?
- madaxe_again 11y agoThen you do agile. It's very suitable for maintenance mode or continuous enhancement.