Waterfall vs. Agile Methodology

From apppm
Revision as of 16:13, 16 September 2017 by Bekis (Talk | contribs)

Jump to: navigation, search

Most software development projects apply either the Waterfall or Agile Methodology. The Waterfall methodology represents the traditional approach, where the development process is conducted in a linear series of events.


Agile and Waterfall are very different and it will not always be possible to choose between them both. Waterfall could be applied to virtually any type of (IT) project. Agile requires specific conditions to be in place to be possible but is not applicable to certain projects – especially those of a large physical nature. Most of the conditions required for Agile to be possible relate to the working environment and practices that can and cannot be employed by the whole project team, not just those responsible for the development. There also needs to be flexibility around requirements together with the capacity to deliver and accept product incrementally.

Contents

Waterfall Methodology

Pros

Cons

Agile Methodology

Pros

Cons

Comparison of the Waterfall and the Agile Methodology

Example of Use

Waterfall Model

Agile Model

Conclusion

References

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox