I like Adrian's approach of different color pens. I've tended to setup an excel spreadsheet with each question/task of the test as a column and each user as a row (can be reversed). That way it is easy to type structured notes and compare them across users quickly.
Try to use a separate note taker. It is hard enough for one person to pay attention to ask sufficiently probing questions based on what they are observing. If you also have to try and capture accurately, you will miss a lot. It is also a great opportunity to involve the PO or a developer or some other non-ux role in the test. Personally, I almost always use the PO as my note taker. They get to experience the session first hand, and changes to the backlog are a conversation between us as we both were there. It also builds support for future testing initiatives.
"Be well, do good work & keep in touch."
- Garrison Keillor
On Thu, Mar 8, 2012 at 12:17 PM, Adrian Howard <adrianh@...>
On 7 Mar 2012, at 03:30, Jon Innes wrote:
> You are correct to avoid lengthy reports. A much better practice for agile projects is to leverage the defect tracking system, especially if it supports screen shot uploads, which most do now. Even if it doesn't just create a link in the defect to a wiki or file server where you can annotate any screenshots that illustrate issues.[snip]
Or even just go to the story board, pick up a card, and go have a conversation with the PO and devs about what's missing (it's often in the definition of "done" for the story rather than in a description of the feature).
http://quietstars.com adrianh@... twitter.com/adrianh
Yahoo! Groups Links
<*> To visit your group on the web, go to:
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to: