My favourite line in the article, because it’s both sad and funny. As for the rest of the article, there are agreeable points but perhaps too antagonistic for some.

I’m not a huge fan of scrum, but I’ve seen it work once or twice. I’d credit it for its communication. I’ve also seen Kanban work for entirety different reasons.

One of the merits of iteration and having a perpetually shippable codebase is being able to validate that you’re solving the right problems and doing it in the way that is best for the customer.

Gone are the days where software behaves as dictated by its creators (who hold a monopoly, unwittingly becoming complacent while resting on their laurels), and the users have little say in how a mass product solves their problem. Unlike the 1990’s, users aren’t going to wait 1 year (plus) release cycles for that next new feature.

The world has become more fast-paced, and ever-demanding. Software back in the day was mostly for nerds (excuse my generalization), but now it’s for everyone. And “everyone” doesn’t care about effort, they just want it to work in a way that doesn’t make them have to think. Consumers and businesses can delete your app or not renew their subscription and try the competitor if your product didn’t provide a profound user experience.

That said, if you release too early and too often, a half-baked MVP will probably be ill-received. The saving grace is that you didn’t trail too far down the wrong path that you can’t pivot, re-center or change focus.

I digress. If the entire industry went back to waterfall next Monday, I don’t think it would work out for everyone.