Agile vs Waterfall: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=Introduction= | =Introduction= | ||
This page is dedicated to constructive banter on the advantages and disadvantages of [[Agile]] | This page is dedicated to constructive banter on the advantages and disadvantages of [[Agile | Agile Development ]] compared to [[Waterfall Development]] techniques. It seems like people push too hard one way or the other usually, and suffer from over structure and under structure. | ||
=Advantages= | =Advantages= | ||
Revision as of 13:02, 28 July 2012
Introduction
This page is dedicated to constructive banter on the advantages and disadvantages of Agile Development compared to Waterfall Development techniques. It seems like people push too hard one way or the other usually, and suffer from over structure and under structure.
Advantages
- It's good for iterative creativity
Disadvantages
- It's good for iterative creativity, but not to get a big project done ON TIME.
- Consider the place Agile is lacking.. and why you'd want a gantt chart... When there are external constraints.. like the delivery of supplies, that contribute to a critical path and require advance planning and an understanding of relationships between initiatives.. say in order to build a house before winter and there's a 3 month lead time on the roofing etc.