 |
The Manifesto for Agile Software Development,
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Articles on Agile Programming:
In the Winter 2002 issue of Methods & Tools, William C. Wake wrote an article "Extreme Programming as Nested Conversations"
In the Summer 2003 issue of Methods & Tools, Lisa Crispin wrote an article "XP Testing Without XP: Taking Advantage of Agile Testing Practices"
In the Winter 2003 issue of Methods & Tools, Matt Stephens and Doug Rosenberg wrote an article "Will Pair Programming Really Improve Your Project?"
In the Winter 2004 issue of Methods & Tools, Gautam Gosh wrote an article "Agile, Multidisciplinary Teamwork"
In the Spring 2005 issue of Methods & Tools, Craig Murphy wrote an article "Improving Application Quality Using Test-Driven Development"
In the Summer 2006 issue of Methods & Tools, Ian Evans wrote an article "Agile Delivery at British Telecom"
In the Summer 2007 issue of Methods & Tools, Tom Gilb wrote an article "What's Wrong With Agile Methods"
Book reviews on AgileProcesses:
TechBookReport - Software Methodologies A range of book reviews on different agile methodologies and agile techniques.
Agile Methodologies
Agile Web Sites
There needs to be more information on the company or what AgileProgramming is, not about how they treat their customers.
|