Project planning in an Agile process differs in one major way from that in the traditional processes; scope. When thinking in Agile terms, it is imperative that we keep the scope part of the scope-delivery date-money equation flexible. After every iteration, we learn and adjust what and when we can deliver the desired features. Keeping that in mind, it is still possible to have a broad goal or most important stories (requirements) addressed in the initial planning.

An example here assumes a 6 months project.

The two timelines depict the clear difference between the planning of software delivery. While a traditional project has checkpoints which are merely technical goals, the Agile project produces a finished set of features every iteration. Since the user feedback is invoked during every iteration, the uncertainties in the expectations are addressed early (instead of 'fixes' at the end of the timeline). Wasteful features and futuristic technical arrangements are avoided. That brings us to an earlier production date, creating some space for additional testing and integration tasks or even adding more features.