CSC/ECE 517 Fall 2012/ch2a 2w5 dp: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 16: | Line 16: | ||
* Customer collaboration over contract negotiation | * Customer collaboration over contract negotiation | ||
* Responding to change over following a plan | * Responding to change over following a plan | ||
=== | === Values === | ||
The Agile manifesto touches upon 4 values that represent the core principles of Agile software development. | |||
#Adaptability | |||
#Transparency | |||
#Simplicity | |||
#Unity | |||
[[File:http://upload.wikimedia.org/wikipedia/commons/thumb/8/89/Agile_Software_Development_methodology.svg/389px-Agile_Software_Development_methodology.svg.png]] | |||
== References == | == References == | ||
<references /> | <references /> | ||
Revision as of 00:57, 19 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.
The Agile Manifesto <ref>Manifesto for Agile Software Development http://agilemanifesto.org/ </ref>
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
Values
The Agile manifesto touches upon 4 values that represent the core principles of Agile software development.
- Adaptability
- Transparency
- Simplicity
- Unity
References
<references />