I've never been in a project in the last 30 years that benefited from a waterfall model.
I suppose that in aerospace (like the space shuttle) it could be beneficial. But even there I have my doubts.
That being said, certain requirements gathering, estimates, and a preliminary UI design can really help close the deal and provide a good prediction of time and cost that is usually a big concern for the one who's paying for your project.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The waterfall methodology is good for a project with clear feature requests only in my opinion.
It would be good to read other approaches compared too 👍
If in doubt use Agile.
I've never been in a project in the last 30 years that benefited from a waterfall model.
I suppose that in aerospace (like the space shuttle) it could be beneficial. But even there I have my doubts.
That being said, certain requirements gathering, estimates, and a preliminary UI design can really help close the deal and provide a good prediction of time and cost that is usually a big concern for the one who's paying for your project.