Shared publicly  - 
 
RT +Takashi Sakamoto UX design process - UX design wiki http://t.co/V0iTzm8

I think the problem with this design process as shown above is, it's basically a waterfall approach. Once the dev team got their hands dirty and does its Agile magic, there are no UX people invited to come along and play ...

+Cesar Torres
7
2
David Roth's profile photoJan Jursa's profile photoKarol Dulat's profile photoStefanie Kegel's profile photo
7 comments
 
I like the model. I think there is a part in the process that should be partly waterfall, that is the macro information architecture. The macroIA should be designed after a careful participatory research phase, and then it should be relatively stable. Everything else can and should be agile and iterative. My two cents (cc +Marco Bertoni )
 
I agree with Stefano that nailing down the IA at a macro level is good. But I'll also bring this back to the UX process. Designing and developing with the user at the center of the process is essential, even when validating an IA document such as a wireframe or site map.
 
I would like to think the developers are involved in the UCD just as the UX people are involved in the Agile development. As a high level process it is not far off - though I think it misses a larger iteration cycle around UCD, Prototype, and Agile.
 
Another good post Jan! I agree with Stefano - setting the gross and fine architecture up front goes a long way to protecting the budget. The place where I see the greatest value in the Agile approach is internal. Trying to anticipate every nuance of the interface and user interaction in the design phase is way too time consuming, and almost certain to generate the "oh crap!" moment when you realize something's been missed.
 
+Matthijs Rouw pointed me towards this PDF http://bit.ly/nujTVu (regarding agile IxD and agile development) by +Lynn Miller. Very interesting. Thanx Matt :)
Add a comment...