There is always good discussion with my colleagues relating to development methodologies. None could be more invigorating than discussions related to Agile development. 

Waterfall is linear and predictable

Waterfall is a sequential process of development that historically includes four distinct stages: analysis, design, implementation, evaluation/metrics and maintenance. Critical downside for this approach is that if there is a major change far along in implementation, code typically needs to be redeveloped from scratch. Instead of predictable, we now have a lot of scope creep.

Agile methods adapt to change

Agile, on the other hand, emphasizes values and principles rather than processes. Moreover, there is less documentation and more collaboration allowing for ongoing refinement of the project. Of critical importance is that this method is adaptable -- a leadership philosophy that encourages teamwork, self-organization and accountability.

Can’t we just all get along

If you can’t decide which may work for you, I’ve found an excellent slideshare presentation by Maria Giudice, CEO and Founder, Hot Studio Inc. entitled “Can’t we just all get along?” that discusses the pros and cons of both methodologies and provides an interesting take on a Waterfall hybrid.

Best

Denice MacDonald