Alasdair MacLeodProject Manager| (retired) formerly Accenture and ClaimsecureSudbury, Ontario, Canada
I must admit I struggle with this question. Some in the Agile camp refer to those who use Waterfall as dinosaurs but I still think each has its place. More often than not I end up using more of hybrid approach with IT projects.
There is no shortage of decision charts which help you decide what is a more appropriate route to go but I am curious how others view how the complexity of a project makes them chose one over the other. I often see Agile favoured as the framework of choice for larger, complex projects but this is one example that I struggle with. If for example there will be many dependencies, integration with external organizations and a clear vision of the end goal, doesn't Waterfall make more sense? I am curious what the opinions of others are in this area. Saving Changes...
One other item to consider is your Finance Dept and their approach, whether they need a complete detailed financial plan up front that Waterfall can provide, or are happy with Agile's more ongoing basis Saving Changes...
There is no bullet proof way that work on every project. Lifecycle vary from one project to another. I use hybrid mid ground. I like to do with Agile but sometimes requirement calls for Waterfall approach. You need to think about how you can deliver most and it help in selecting correct one. Mid ground mostly work
I have to recognize that I only walk through this post to review some of the colleages answers... :) Saving Changes...
Anish AbrahamPrivacy Program Manager| University of WashingtonAuburn, Wa, United States
In my organization, we normally follow hybrid approach. Anyway it depends on the project. Saving Changes...
Anton OosthuizenSenior Business Analyst / Project Manager| Self EmployedPretoria, Gauteng, South Africa
Seems like the majority uses a hybrid approach, as do I. I normally find that the two touch at the development/delivery level. Doing pure agile for development is usually 'easy' but there could be some issues with during delivery that does not allow for a 'pure' agile approach. Take a look at https://www.projectmanagement.com/videos/4...roject-Delivery Saving Changes...
