CSC/ECE 517 Fall 2012/ch2a 2w5 dp: Difference between revisions
		
		
		
		Jump to navigation
		Jump to search
		
| Line 1: | Line 1: | ||
| == Agile Software Development == | == Agile Software Development == | ||
| === History === | === History === | ||
| === 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. | |||
| He defines success into 3 types: | |||
| # Organizational | |||
| * deliver value and decrease costs to increase return on investment. | |||
| * focus development efforts on the core value that the project provides for the business.  | |||
| * release most valuable features first and release new versions frequently. | |||
| # Technical - producing elegant and maintainable code. | |||
| # Personal - a fun and intrinsically rewarding project in which developers devote their passion. | |||
| === Manifesto === | === Manifesto === | ||
| From [http://agilemanifesto.org Agile Manifesto] | From [http://agilemanifesto.org Agile Manifesto] | ||
Revision as of 01:20, 18 October 2012
Agile Software Development
History
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. He defines success into 3 types:
- Organizational
- deliver value and decrease costs to increase return on investment.
- focus development efforts on the core value that the project provides for the business.
- release most valuable features first and release new versions frequently.
- Technical - producing elegant and maintainable code.
- Personal - a fun and intrinsically rewarding project in which developers devote their passion.
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