I think the conflict between design and agile development methods is best understood by reflecting on the values conflict between the two disciplines.
Here's a full list of the principles of agile development: http://agilemanifesto.org/principles.html These principles are ones I think designers and developers/technolgists will agree on in most cases: Simplicity--the art of maximizing the amount of work not done--is essential. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. These two fight design values the most: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Working software is the primary measure of progress. This one has some risk because technology is "excellent", but design is merely "Good"... Continuous attention to technical excellence and good design enhances agility. Ten years ago software development was in a crisis. Agile methods have made a significant, positive impact on software development quality and productivity. As somebody with a software development background who is currently working both sides in the development of social software systems in a research environment, I found this question interesting, and I hope the response is helpful. -- Sean P. Goggins http://www.goggins.com ``Design is what you do when you don't [yet] know what you are doing.'' -- George Stiny, Professor of Architecture, Massachusetts Institute of Technology, "The game is a lot better because he played it, and I think that's the criteria that matters most." --Mike Ditka on Brett Favre http://www.wisconsinidea.wisc.edu/history.html ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
