> Should we go back to Waterfall? In many areas we are already doing waterfall, except it is a sin to call it that way and we must pretend we are doing agile.

> Should we go back to Waterfall? In many areas we are already doing waterfall, except it is a sin to call it that way and we must pretend we are doing agile. Let me give you two examples: - Contractual requirements. If you have a contract with a customer to build X, no matter how much agile lingo you use, you are basically doing a waterfall. - Legal requirements. Same as above. For instance, there is very little flexibility in being GDPR compliant.