It is awesome how many different ways of doing project management there are. If you have not heard of using iterative with agile for doing projects especially for software projects, then I highly suggest you check out the links at the bottom of the page.
A review of the 2010 Standish Chaos Report refers to project management styles and their success rates. You can quickly see that using Agile or Iterative will give you a 20% boost on software project success over a traditional approach. By traditional approach, let us assume that is your five-process PMBOK style project where you start at the beginning and works through to the end with lots of control/execute loops.
I have also attached a link from the University of Florida – a power point – that explains what the iterative approach is and it makes tons of sense if you are working on a software project. On the other hand, if you are working on a building project an iterative approach will not work; simply because you need to have the project defined before you start.
Software projects by their nature are easier to deal with than a building project. Infrastructure means purchasing, means delivery times, means, coordination of resources, etc. While in typical software projects, you have got resources dedicated for the duration of the project. The project period may be fixed, but the iterative project approach still applies, even more so. If you blend the iterative and agile style with a daily scrum, you will have a better than 20% chance of success over any other style. On top of that, you will enjoy benefits like an energized and excited team, a thoroughly delighted customer a management group that feels like they are on top of the world, and a successful organization.
Why not make your very next software project an agile/iterative project. What have you got to lose? What could you gain? Improved morale, better customer retention, greater benefits for the business, happier staff.
Definite must reads for Iterative Project Management