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

4058Re: [agile-usability] Re: Leverage a small UX team?

Expand Messages
  • Jon Dickinson
    Mar 8, 2008
    • 0 Attachment
      On Mon, 03 Mar 2008 23:14:03 -0000, timkieschnick <tim.kieschnick@...>

      > I like the idea of showing live user testing to the stakeholders,
      > but it sounds problematic in terms of being able to show a
      > representative sample of users to the stakeholders--I wouldn't want
      > the stakeholders to see the one outlyer test, and I don't know how
      > I'd show them 4-5 users in one demo.

      I can see that it would be a risk if the results of one bad
      test/demonstration to the stakeholders sends the team off in the wrong
      direction for an entire sprint.

      From reading your excellent experience report:
      http://timiti.blogspot.com/2008/02/user-research-as-commodity.html, the
      following passage strikes me as providing two possible solutions:

      "Every other Thursday morning, four or five brokers (our target audience)
      would show up at our offices in Pasadena. Our user research specialist
      would work with each participant for about an hour. While this testing
      took place in Pasadena, we piped audio and video of the testing up north
      to Pleasanton so the team could watch in real-time and IM questions and
      comments to the moderator in Pasadena."

      1) Persuade the stakeholders to spend the entire morning at the end of the
      sprint observing the usability tests. This is my ideal.
      2) Have the stakeholders sit in as observers on the test with the last
      participant. If the results of this test turn out to be radically
      different to the earlier tests, you have the results of the previous tests
      to demonstrate that this was the exception.

      If the stakeholders are limited to observing a single test, it is probably
      worth giving them a half hour demo of the work completed before the
      usability test so they have an initial idea of what work has been
      completed. You don't want one bad test to negate all the hard work the
      team has performed during the sprint.


      Jon Dickinson
      Accolade Consulting
    • Show all 21 messages in this topic