Loading ...
Sorry, an error occurred while loading the content.

Re: [agile-usability] Prototyping Tools

Expand Messages
  • chris@pehura.com
    I ve found calling it different names problem way to common. Let s do RUP implemented as water fall. Let s do Agile, and do anything we dang well please. The
    Message 1 of 43 , Jan 10, 2008
      I've found calling it different names problem way to common. Let's do RUP implemented as water fall. Let's do Agile, and do anything we dang well please.

      The biggest problem I've found is that a person comes up with one approach and only one approach despite the context. And after experiencing the fun (fun as having each fingernail slowly pulled out one at a time) to clean up the mess left behind, I always provide alternatives backed up with alternatives backed up with alternatives. I've seen the problem in every effort I've been in. The difference being the level of impact.
      Chris Pehura

      -----Original Message-----
      From: Ron Jeffries <ronjeffries@...>

      Date: Thu, 10 Jan 2008 16:43:49
      Subject: Re: [agile-usability] Prototyping Tools

      Hello, Brian. On Thursday, January 10, 2008, at 1:37:36 PM, you

      > In the end, I've worked with damn near every software dev
      > methodolgy there is, and they all are
      > the same.

      Maybe you've just done one methodology and called it different

      Ron Jeffries
      This is how I develop software.
      Take the parts that make sense to you.
      Ignore the rest.
    • Brian Weiss
      First off, I d just like to say I love reading all the opinions out there as I m on an island here... So have we reached violent agreement yet? :D Considering
      Message 43 of 43 , Jan 17, 2008
        First off, I'd just like to say I love reading all the opinions out there as I'm on an island here...
        So have we reached violent agreement yet? :D
        Considering there are myriad ways to present wireframes and flows...whatever works for you, well, works for you. So far, at this place I'm at, user studies done with Flex/Flash based prototypes that look close to a branded/finished product have worked very well. The feedback has been excellent and it seems quicker to me to get the users focused and into the scenarios. That said, and again for me, the paper wireframes have been better at getting business requirements on the table with Stakeholders and other internal partners as they get hung up on the interface of the prototypes too much. The nice thing about alternatives is you can try them all...
        We all did get a good laugh out of the Flex "paper" skin Frédéric Monjo mentioned: http://fleksray.org/skins/edding/Edding.html and actually might try it out.
        And if a Stakeholder asks "Is this what we're getting?" I've decided to say "Yes. Yes it is."

        ----- Original Message ----
        From: Fred Beecher <fbeecher@...>
        To: agile-usability@yahoogroups.com
        Sent: Tuesday, January 15, 2008 3:39:08 PM
        Subject: Re: [agile-usability] Re: Prototyping Tools

        On 1/15/08, thomas lissajoux <thomas@systemesagil es.com> wrote:

        I think we're getting back to what Brian Weiss mentioned at
        the beginning of this thread : having hi-fi prototypes too often
        leads to stakeholders pointing to differences and details in
        production work.

        So this leads me to some other question ?
        What does prevent user experience testing to be conducted with
        paper prototypes (+ trend boards + visual identity sketches) ?

        My own opinion : not much.

        If you're doing a highly interactive site with a lot of rich interactions, you're missing a whole lot. If you're just doing a standard Web page where you click from page to page, then you wouldn't be missing much.

        Interactive (notice how I didn't say "high fidelity"... I'll get to that in a bit) prototypes yield much more accurate information in user testing of Web sites that rely on rich interactions. Why? Well, it's all about context. Paper is NOT the context rich interactions are meant for, and people will correspondingly be confused. For simple Web sites, it's close enough. If you really want to know whether a rich interaction is usable or not, it needs to be in an interactive format if you want to get reliable, actionable data from user testing.

        Responding to your musings about hi-fi prototypes.. . I think that fidelity is only *one* aspect of a prototype. *Interactivity* is the other. You can have a lo-fi interactive prototype, which is typically what Axure produces... essentially interactive wireframes. You can also have hi-fi prototypes that are low on interaction, such as printed JPGs. In my experience, I've found that stakeholders respond to lo-fi interactive prototypes pretty much as they do wireframes. I have been in some situations, however, where the interactivity was communicated much more effectively than in wireframes, which led to constructive feedback from stakeholders *pre* development.  

        - Fred

        Never miss a thing. Make Yahoo your homepage.
      Your message has been successfully submitted and would be delivered to recipients shortly.