Wow! where to begin here. Jeff, Yup, I've had way too many hours in agile. Yup, they could definitely run better and they can produce results. I'm not saying that they can't produce.
Mark hit it on the head, it is a developer/engineering inspired and valued process. It is for THEM! It is not about us, for us, by us, or valuable to us. This is my #1 issue with agile. And all the things you say below about getting design into agile, are hacks! They are not the best of what we can do, but what we can do in THEIR framework. Yes, I've done research, I've done sketching, I've done all the design you can in an agile framework. When it's worked best is when I did it before the product development team launched their agile program and then integrated my validation cycles into iteration periods. I also think that we might have different ideas about what design is or isn't. Design is cultural to me. not in the sense that it is culturally relative, which it is, but in the sense that design has its own culture. That culture if you will is part of the value (and values) that it brings into the world and when you try to force it into another cultural model, you are degrading its value. Your laundry list of tasks, itself, speaks to that degradation. What I do as a designer is not a list of tasks. It is much more than that list, but is part of a whole and part of a relationship with others who are focused on that whole. Bill's talk this weekend (I can't wait for people to see it), shored up my zeal in this regard so much more. Unless you can first see the whole of what you are building, you shouldn't start building. As for Autodesk. Fine company, great sponsor. I don't know much of their software, but when you say "success" you have to say what you mean. I know for my part that I would never put Autodesk in the same league when it comes to design as say Um! Apple, BMW, EA, Google, Lexus, IDEO, frog, etc. (though many of those companies use Autodesk products). As I said in my first post. Story telling is really important. Modeling a whole including its production, distribution and evaluation really needs air to happen. -- dave On Feb 12, 2008 7:38 AM, mark schraad <[EMAIL PROTECTED]> wrote: > What is rarely said explicitly, is that agile is a development process. It > borrows heavily from design in its use of iterations, early prototypes and > review cycles. This becomes pretty apparent when you speak to agile > consultants, who lately have found that, and I quote, "our clients really > like it when we pair design on the front end with our process". > Mark > > > On Feb 12, 2008, at 2:15 AM, Jeff White wrote: > > There are ways to do > > real design in agile - incorporating user research, concept ideation, > > exploration & critique, and true iteration based on things like > > usability testing and design leadership > > > -- David Malouf http://synapticburn.com/ http://ixda.org/ http://motorola.com/ ________________________________________________________________ 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
