> then it benefits from _some_ waterfall planning. Meaning to think before the work begins about the approach being taken, all of those dependencies, and who you need to engage and when... tada, you've made a GANTT chart in your head and are now waterfall because you put some thought into the dependencies and the order of execution.
Agile does not mean that you should forego all of this and code first, think later. What you describe does not oppose Agile and Waterfall.
Agile does not mean that you should forego all of this and code first, think later. What you describe does not oppose Agile and Waterfall.