Which could possibly be the most common mistake on the history of the adoption of iterative and incremental development?
Craig Larman proposes an answer to such a question in his book Agile and Iterative Development: A Manager’s Guide:
“Sure, we don’t apply the waterfall—everyone knows it doesn’t work. We’ve adopted <iterative method X> and are into our first project. We’ve been at it for two months and have the use case analysis nearly finished, and the plan and schedule of what we’ll be doing in each iteration. After review and approval of the final requirements set and iteration schedule, we’ll start programming.
This profound misunderstanding, still superimposing waterfall-inspired, big up-front analysis and planning (predictable manufacturing) values onto iterative methods, is one of the most common mistakes that new iterative and agile method adopters make.”
Based on the number of times and frequency I have found such a misunderstanding, certainly, make it a well positioned candidate for such a place in the history of our trade.