The War between Waterfall and Agile; must we?

When you spend a long enough time in any profession, you see fads come and go.  The flames of change get fanned by software companies, industry publications, academic theorists and a host of other protagonists, and we’re off to the races chasing the latest and greatest (insert your own here).  The current buzz in the project management and software development worlds swirls around Agile Methodologies.  Camps divided, swords drawn, the traditionalist waterfall proponents vs the new age agilest.  Let the games begin!    Who’s right?  Who will dominate? 

When I take a step back from the warring sides, it becomes clear that the answer isn’t one or the other, it’s what is best in this situation or another.  What I will offer is the following startling revelation:

1. Not all waterfall projects fail.  Yes, there is plenty of media coverage of the 3 year $100,000,000.00 projects that sent Company XYZ into bankruptcy.  But what about all the quiet projects that use waterfall and are a rousing success.
2. Not all agile projects succeed.  Introducing agile is more of a mind shift than just a change in methodology.  This cultural change causes upheval; be prepared for resistance.

Understanding the corporate dynamic, adaptability to change, and culture should never be overlooked when contemplating this type of mind shift.  It is through open discussion and analysis that the right way will be found, not blind allegiance to one or the other.

I’ll be posting more on this subject in the future.  Keep watching