CSC/ECE 517 Fall 2009/wiki3 7 f1: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
== Agile vs Traditional Methodologies == | == Agile vs Traditional Methodologies == | ||
The agile manifesto focuses on | |||
That is, while there is value in the items on the right, | *''' Individuals and interactions''' over processes and tools | ||
*'''Working software''' over comprehensive documentation | |||
* '''Customer collaboration''' over contract negotiation | |||
* '''Responding to change''' over following a plan | |||
That is, while there is value in the items on the right, agile values the items on the left more. The items on the right are what the traditional design methodologies emphasise on. | |||
Revision as of 00:54, 10 November 2009
This wikipedia article focuses on how Agile software development methodology can complement other traditional design methodologies like the waterfall model. We take a few software development practices from the customer, management and development points of view, focus on the limitations of the traditional software development model and discuss how agile development methodologies can be used to complement/overcome its limitations.
Agile vs Traditional Methodologies
The agile manifesto focuses on
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
That is, while there is value in the items on the right, agile values the items on the left more. The items on the right are what the traditional design methodologies emphasise on.