Sure, but that's failure due to not getting the business requirements right. If the code had been hastily thrown together with no regard for process it's hard to believe it would've produced a better outcome.
Well it's priorities, no? If you spend the time to get the code right, you're not spending time validating your business or talking to customers. And indeed "getting your code right" is a very common excuse to not ship.
I suppose I'm enough of a traditionalist to believe the two skillsets - one being validating a business/talking to customers and the other being the actual software development side of things are sufficiently different that it's extremely rare that one individual is going to handle them both well.
