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

From Expertiza_Wiki
Jump to navigation Jump to search
Line 2: Line 2:
=== History ===
=== History ===
=== Why Agile? ===
=== Why Agile? ===
James Shore states that the benefit for developers to follow a Agile software development process is to deliver successful products to the client or customer.
James Shore and Shane Warden ##The Art of Agile Development | Label### 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
* deliver value and decrease costs to increase return on investment.
#* Deliver value and decrease costs to increase return on investment.
* focus development efforts on the core value that the project provides for the business.
# Technical
* release most valuable features first and release new versions frequently.
#* Elegant and maintainable code is produced.
# Technical - producing elegant and maintainable code.
# Personal
# Personal - a fun and intrinsically rewarding project in which developers devote their passion.
#* Developers find the project fun and rewarding which lead them to be intrinsically motivated and devote passion to the work.
 
=== Manifesto ===
=== Manifesto ===
From [http://agilemanifesto.org Agile Manifesto]
From [http://agilemanifesto.org Agile Manifesto]

Revision as of 01:30, 18 October 2012

Agile Software Development

History

Why Agile?

James Shore and Shane Warden ##The Art of Agile Development | Label### 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.

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

Subsubsection heading

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