CSC/ECE 517 Fall 2012/ch2a 2w5 dp: Difference between revisions
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
=== History === | === History === | ||
=== Why Agile? === | === Why Agile? === | ||
James Shore and Shane Warden | James Shore and Shane Warden <ref>Shore, James and Warden, Shane. ''The Art of Agile Development''. O’Reilly Media, Inc., 2008, p. 4.</ref> state that the benefit for developers to follow a Agile software development process is to deliver successful products to the client or customer. | ||
He defines success into 3 types: | He defines success into 3 types: | ||
# Organizational | # Organizational | ||
| Line 18: | Line 18: | ||
* Responding to change over following a plan | * Responding to change over following a plan | ||
==== Subsubsection heading ==== | ==== Subsubsection heading ==== | ||
== References == | == References == | ||
{{reflist}} | {{reflist}} | ||
Revision as of 01:32, 18 October 2012
Agile Software Development
History
Why Agile?
James Shore and Shane Warden <ref>Shore, James and Warden, Shane. The Art of Agile Development. O’Reilly Media, Inc., 2008, p. 4.</ref> state that the benefit for developers to follow a Agile software development process is to deliver successful products to the client or customer. He defines success into 3 types:
- Organizational
- Deliver value and decrease costs to increase return on investment.
- Technical
- Elegant and maintainable code is produced.
- Personal
- Developers find the project fun and rewarding which lead them to be intrinsically motivated and devote passion to the work.
Manifesto
From Agile Manifesto
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan