I've found that in Agile (as in most environments), unless there is an already existing respect for the importance of UX, that one needs to be first and foremost an advocate for UX.
The role is not confined to a title really. I have found the need to push CE and time spent on user analysis and testing. In Agile I've found this much easier due to the nature of the methodology. Hold workshops, present all ideas, get feedback, collaborate collaborate collaborate. Get feedback, iterate, Get more feedback. An Experience Architect is the best term I could conjure. But it involves much more than interaction design / visual design. The Agile methodology is very user centric, however, many institutions are still to practice this part. And this is where we come in. To tell them what "involving the user" is all about. Contextual Enquiry is only going to happen if you make it so. You need to be an analyst, and a bit of a Project Manager, and of course a designer. You need to drive the vision towards usability. Erm, yes, so what I'm saying is - Agile is a brilliant environment to advocate usability. However, a methodology needs to be lived and breathed by an organisation before we can actually benefit from such concepts. I suppose that I have the question: How many "Agile" organisations practice real Agile? How many butcher it? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=48601 ________________________________________________________________ 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
