Terminology nitpick: this article is not about planning, it's about estimation.
Estimates, plans and commitments are three different things (see http://www.amazon.com/Software-Estimation-Demystifying-Pract..., which is the best book I've read on the subject).
The problem with estimation in many cases is that people who dictate requirements often dictate commitments as well, and do so without estimation-based feedback. In other words: "Your ten-week 'estimate' isn't acceptable; we have to have this done in seven!"