Without the end-user involved in the entire development process, with no BA, it is still waterfall aka 'fake agile'. Creating a division in software developmen

Without the end-user involved in the entire development process, with no BA, it is still waterfall aka 'fake agile'. Creating a division in software development creates a gap. Shouldn't even be sitting in a separate office / section of office / in that state of mind. It is not "in software development." It is product development.