New answers tagged


It does make sense in some scenarios but I think this is not a question which one is better. The real question is which one you are better at? On the other hand, you can learn and be master of Agile methodologies but your software architecture, team structure, size, geographical distribution, quality processes, ... may not suit agile.


Waterfall works great if you know exactly what the code needs to do and can articulate it in such a fashion that your developers clearly and unambiguously understand what is required of them. Most clients are not able to describe what they want/need that well. There are some situations where Waterfall is and should be the methodology of choice, but ...


No, because the computers and software environment that the application runs on will continue to change even whilst the code is frozen. The operating system continues to evolve with patches and fixes, as well as the devices and drivers. Just when you think you have reached the point of no known bugs, AMD or nVidia will release a video driver update that ...


It is possible to consistently deliver bug-free software, given sufficient discipline and shared team culture. (And well-factored modular code, a comprehensive suite of automated tests, inspecting defects and adapting your process, and a lot of other things that require effort and humility but pay back thousandfold) But doing this, you don't generally set ...

Top 50 recent answers are included