Tbh I know what he is saying. Software that is speced up by BA's and driven by their requirements tends to end up being really bad software. The best software

Tbh I know what he is saying. Software that is speced up by BA's and driven by their requirements tends to end up being really bad software. The best software is built up over time as demand arises for those features. Create the feature requests as they are required and implement the requests. I think one of the major causes of why this type of thinking ends up building bad software is that BAs include literally every corner case they can think of. Ends up being extremely complicated right from the start. Then they miss other requirements. If you build by evolving software from a simple beginning just to scratch an itch, you learn the true requirements from experience. Learning about the optimal architecture from experience as they go. Hard to do when your working off a software dev contract. Fairly easy to do if your building a product. It's cathedral vs bazaar.