This article assumes a very narrow definition of "long-term plan", yet doesn't give that definition to the reader. Here are some clues towards that definition:
> Instead of rewarding teams for delivering useful, profitable features, companies which worship conformance to plan reward developers for features on time and within budget
"The plan does not look at the usefulness of work done. The plan decides in advance on a time frame and budget for each feature."
> Consequently, to make up for these delays, teams are pressured to deliver the next feature in less time than they originally estimated.
"The plan must be rigid with respect to unforeseen bugs. Scope or time frame cannot be adjusted."
> Consequently, long-term plans either force you to stick to useless features or pressure the team to accelerate the following features to compensate for the delay created by listening to feedback.
"The plan does not allow adjustments based on feedback."
> Instead of rewarding teams for delivering useful, profitable features, companies which worship conformance to plan reward developers for features on time and within budget
"The plan does not look at the usefulness of work done. The plan decides in advance on a time frame and budget for each feature."
> Consequently, to make up for these delays, teams are pressured to deliver the next feature in less time than they originally estimated.
"The plan must be rigid with respect to unforeseen bugs. Scope or time frame cannot be adjusted."
> Consequently, long-term plans either force you to stick to useless features or pressure the team to accelerate the following features to compensate for the delay created by listening to feedback.
"The plan does not allow adjustments based on feedback."