Many of the Agile development teams I've seen (that are smart enough to make an interaction designer a core part of the software development team) move in the same direction Bryan has. The basic principle that seems to work best is that the design will be specified in a format that developers can use. So if it's a Rails/Ajax application, they're doing their design exploration and prototyping in dHTML. If the front end is flash, then that is what the prototype and design are executed in as well.
I've personally tried many the intermediary steps like the Adobe products or modeling tools like Caretta or iRise, but eventually concluded that there wasn't enough spare time to execute 100% throw away prototypes on Agile projects. I also haven't found the single tool that a designer can use to turn a prototype into a working web application. For some CRUD applications, I've recently seen situations where an interaction designer paired with Rails developer produced an amazingly rich prototype in about 2-3 weeks. In several of those cases, much of the prototype code base survived into the actual production application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=24306 ________________________________________________________________ *Come to IxDA Interaction08 | Savannah* February 8-10, 2008 in Savannah, GA, USA Register today: http://interaction08.ixda.org/ ________________________________________________________________ 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
