CSC/ECE 517 Fall 2010/ch6 6c sg: Difference between revisions
No edit summary |
No edit summary |
||
Line 9: | Line 9: | ||
== Why do estimation == | == Why do estimation == | ||
== Traditional vs Agile approach == | == Traditional vs Agile approach == | ||
== References == | |||
*[http://agilemanifesto.org/] |
Revision as of 04:42, 17 November 2010
Introduction
Agile software development is a conceptual framework for undertaking software engineering projects. Agile methods try to overcome the weakness found in Classic software development methodologies such as the waterfall model by using an iterative and incremental development approach. Most of the agile methods try to minimize the risk involved by developing the software in smaller time frames also known as iterations. Each iteration lasts for around one – four weeks. The characteristics of Agile manifesto published in 2001, by a bunch of software engineers can be summarized as follows: ( link) Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan.