Does Agile Work for Short-Term Projects Only?

We know Agile as an iterative approach to managing projects and change, based on building plans for short intervals only and hitting the reset button at their end to start again from scratch.
Should this imply that long-term planning and management of large-scale projects is not possible with Agile methodologies?

This line of thinking would have fundamental flaw an assumption, that good results actually stem from a plan. As if making the decision to achieve a given result was equivalent to having this result materialised.
Isn’t it more likely that it is the process itself that forms the outcome of a project? And that putting an emphasis on the project execution and caring for details should therefore bring better results than having a great master plan?
Does it not make sense then to have as many opportunities to rethink the next steps and to exercise many short-term goals, rather than complete a large plan without any critical view on it along the way?
Requirements will change for long-term projects even more-so than for short-term ones, so having to re-evaluate the best way forward a number of times cannot be a bad thing, can it?
Agile therefore greatly supports long-term jobs with the following:

Multi-level verification makes for a better product

Improving globally while evaluating locally

Being Agile means great flexibility

Though it may be easy to associate Agile with sprints and quick action taking, it’s worth keeping in mind this can be used to great advantage for large scale and long realization term projects.

First posted on the Kanban Tool Blog.