FAQ - Which Methodology Is Best, Waterfall or Agile?
A war of wills has begun between those who say all projects should be Agile projects, and those who say all projects should be traditional waterfall projects.
The war between Waterfall and Agile is silly, because we have lost sight of what each methodology/philosophy brings to our projects. The Waterfall-Agile debate should not be a Win-Lose scenario.
Do you agree with these statements?
- Traditional "waterfall" project management works best when Scope, Time and Cost are known up front, and change is minor during the life of the project.
- Agile project management works best when Scope, Time and Cost are uncertain, and change is frequent during the life of the project.
- We can realize the greatest benefits of both methodologies when we analyze our project, apply Waterfall processes to phases that are predictable with little change, and apply Agile processes to phases that are uncertain with much change.
If you agree with the statements above, then you believe in the promise of Hybrid Project Management. That's the future of project management. Traditional top-down (Waterfall) processes will be used where there is predictability. Agile processes will be used where there is uncertainty. That's where the real gains in will occur, for scope, time, cost and customer satisfaction.