Peirre Roberge wrote: >> 2) Engineering-Focused (4 months): Agile programming team develops >> the product using the prototype as a target, with occasional light >> input from the design team but mostly focusing on solving and >> innovating tech solutions. ****Expose the development product >> regularly to a small user test base and collect feedback.**** >> Meanwhile, the design team begins conceptualizing the version 2.0 >> product. > > > My question: > Could you tell me more about the type of feedback the developers > were getting from the users to which they were showing the product > being developed?
It was primarily feature and usability feedback (not bug or performance testing, if that's what you're asking, although that was happening too). We learned more about what they found useful and not useful, what they understood conceptually and what was confusing, patterns of usage and learning. Things that influence the product and UX design itself. Anjali R Arora wrote: > This does sound like a dream project: getting 4 months to research > & design! The way I see it, this is an ideal process even from an economic point of view: The customer gets to play a key role in influencing exactly what they're going to get before any coding is done -- they can actually see a simulation of the final product months ahead of time -- without having to deal with a lot of "but we can't do that" backtalk from the programmers ;-). The prototype can be used to earn additional buy-in, feedback, and funding in the organization. Usability testing can be done on a prototype. And the engineers don't have a lot of abstract "requirements" to either collect or to try to fulfill. The extra time planning the UX saves tons of coding and testing time later. W Evans wrote: > My baggage? I have gone to 2 conferences and have has 3 all day > workshops on > Agile + UCD. My money would have been better spent on Beer. All > were either > conducted by either Agile centric software architects with little > or no > understanding or experience with real UCD - another was from a UCD > guru who > lectured for a day on the process - but had never actually been the UX > Architect on an Agile project. Hear hear. Many tech-focused Agile people think Agile+UXD means "hire a good designer to slap a UI on the product at the end", while much of the UX-focused literature is "it would be great if I someday had a chance to help those poor Agile developers". -Cf Christopher Fahey ____________________________ Behavior biz: http://www.behaviordesign.com me: http://www.graphpaper.com ________________________________________________________________ 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
