What are your thoughts on Interaction Design and the Agile Environment? Here’s my experience of how extreme programming and design mix:
1) Product requirements are one thing today, another tomorrow, based mainly on strategic (not user) feedback 2) Weekly iteration cycles allow 4-5 days for research, prototyping and documentation of design 3) Little time is left for contextual inquiries - the product becomes the "company’s" vision rather than the consumer’s asked-for solution 4) “Featuritis” is a full-blown epidemic 5) Redesign of the entire system is needed every time a new feature changes how the ones already in place interact What are your thoughts on how a "start-up interaction designer" can... 1) Keep ahead of developers and still design useful interactions 2) Build flexibility in their design in order to prevent constant redesigning when new features are introduced 3) Keep an open dialog with users in the most time and budget- efficient way It sounds like a tall order, but as I was reading through the different postings it became clear to me that if there is an answer out there ... you guys have it! :) Thanks, Loredana ________________________________________________________________ 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
