On 9 Jan 2008, at 14:54, Matthew Nolker wrote: > 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. [snip]
I too have seen this working very well. With very occasional exceptions[1] I don't produce any sort of "functional" or hi-fi prototypes. Everything happens on the implementation platform. This includes tools and domain-specific languages to help the designers more effectively work on that platform. Lots of lo-fi work (Paper prototypes, white boards, post-it notes, etc.) and being in the same room as everybody else handles one part of the testing/communication tasks the artefacts/documentation used to handle. Having a bunch of good development practices in an environment adapt at handling change giving a very rapid turn around when implementing new features copes with the situations I would previously have used functional prototypes. Seems to work well. Cheers, Adrian [1] Basically when it is a _lot_ faster to prototype something for user testing in something else, rather than create it using the implementation platform. This happens very infrequently for me (I mostly live in the web development domain, so this may be easier for me than it is for some other folk.) ________________________________________________________________ *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
