> Contrast that to software engineering, where beginning before you have requirements is seen as a requirement of being agile. Not that I agree with all the ag

> Contrast that to software engineering, where beginning before you have requirements is seen as a requirement of being agile. Not that I agree with all the agile ideas, but if I remember correctly we had a process already which was supposed to start with "gather all requirements" and then the rest follows. It was called waterfall development and didn't work so great either, mostly due to the 'all' part in requirements being violated all the time in practice.