Iterate Iterate Iterate!

Adam Fridman writes about the "massive" downside of agile software development for Inc. magazine. He is right to acknowledge the risks involved in any custom software project. Without knowing how software projects of any size can fail, you can't modify scrum well because you don't see the difference between a catastrophic derailing vs an intelligent tweak. The way Adam assumes these risk are fatal flaws to agile seems to be throwing the baby out with the bathwater.
The articles biggest flaw is the way it propagates a Big Software Myth: clients know what they want.

Feedback is an essential part of every software project, and claiming that waterfall provides superior predictability doesn't hold water (see what I did there?) in reality. Waterfall's additional plans and requirements tomes provide the illusion of predictability but in reality are themselves the cause of much waste. The wise executive knows this and sets roadmaps of long and short-term goals, and adapts along the way as milestones are hit. Build something and inspect it. Adapt your plans accordingly. inspect adapt iteratively and you provide the highest value for the lowest cost.