On 4 Nov 2008, at 20:58, Elizabeth Whitworth wrote:
[snip]
It would be great to hear the experiences of others on this list in
resolving design and agile methods.
[snip]
The biggest change I've noticed in my own behaviour was a move away
from producing "documentation" in the form of hi-fi wireframes,
prototypes, etc. - instead spending much more time in conversation
with individuals/groups, producing lo-fi prototypes, and explaining
the "whys" behind decisions face to face with the team.
Much more of a UX educational/evangelist role than I was previously
used to.
I think somebody already mentioned Jeff Patton's article on emerging
best practices - most of which agree with my experiences:
http://agileproductdesign.com/blog/emerging_best_agile_ux_practice.html
The main difference in my personal experiences is I find as much need
for UX input on the developer side of agile teams as on the customer /
product owner side. For me I find it more of a bridging role.
The abstractions we create in the design need to run through into the
code that's built. This is especially important in agile teams when
the design->implementation cycle is so short it can go quickly off the
rails if folk aren't keeping an eye on those issues. Having more UX
experience on the dev side helps a hack of a lot here - hence me
spending more time doing educational/evangelism.
Possibly that's just my personal experience speaking since I've got
got a pretty heavy development background myself - but I've seen
problems when the UX folk have just kept on the customer side.
Cheers,
Adrian
________________________________________________________________
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
