CSC/ECE 517 Fall 2012/ch2a 2w5 dp: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 28: Line 28:
#Unity
#Unity


[[http://i.imgur.com/J6Rxz.png]]
[[File:Agile_poster.png]]
 
==== Adaptability ====
==== Adaptability ====
==== Transparency ====
==== Transparency ====

Revision as of 02:43, 22 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:

  1. Organizational
    • Deliver value and decrease costs to increase return on investment.
  2. Technical
    • Elegant and maintainable code is produced.
  3. Personal
    • Developers find the project fun and rewarding which lead them to be intrinsically motivated and devote passion to the work.

The Agile Manifesto

The Agile Manifesto <ref>Manifesto for Agile Software Development http://agilemanifesto.org/ </ref> is a set of 12 principles that provide a foundation for agile methodologies.

The core principles of the manifesto are as follows:

  • 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

There are four concepts that represent the main values of Agile software development.

  1. Adaptability
  2. Transparency
  3. Simplicity
  4. Unity

Adaptability

Transparency

Simplicity

Unity

Best Practices

Popular Agile Methods

References

<references />

Retrieved from "https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2012/ch2a_2w5_dp&oldid=67769"