Usability IRC Meeting#5

http://groups.drupal.org/node/166059#comment-587219 for the summary

[22:00:16] Hello All!
[22:01:56] dcmistry: heya
[22:02:24] hey hello
[22:02:34] Bojhan Yoroy: Let's get started!
[22:02:37] :)
[22:03:13] hey
[22:03:14] privet
[22:03:18] So for today
[22:03:20] and the agenda for today is?
[22:03:27] We wanted to discuss how-to test drupal
[22:03:33] Yes
[22:03:43] To talk more about the Verify gate
[22:03:46] yoroy: the verify gate.
[22:04:28] So, I have a few comments on the draft
[22:04:44] I think some wordings are off in the draft :(
[22:04:59] or may be I am not understanding it correctly
[22:05:17] dcmistry: sure
[22:05:41] e.g. we want to prevent requiring (up fron) usability testing in this case: MINOR OR NORMAL USABILITY BUG FIXES?
[22:06:15] seems like that we don't care about a normal usability problem
[22:06:33] dcmistry: Does it?
[22:07:03] to me, yes
[22:07:08] dcmistry: I spend a lot of time on normal usability problems :)
[22:07:14] ha ha ha
[22:07:16] exactly
[22:07:38] so this comes across we care only about critical problems
[22:07:46] and we will ignore about other problems
[22:07:46] dcmistry: hmm
[22:07:49] dcmistry the intent is to discourage requiring up front testing in order to make design decisions or before an issue can be rtbc
[22:08:07] I guess, it is just a wording issue
[22:08:19] dcmistry: Well, we do care - but I think we discussed this earlier - that we want to take care of our resources too.
[22:08:53] Ok… I will make some tweaks (minor ones)
[22:08:56] to the draft
[22:08:59] but moving on...
[22:09:14] Bojhan: continue ...
[22:09:30] dcmistry: ok er
[22:09:32] so
[22:09:35] I just drafted something
[22:09:45] made it into a book, which was silly of me
[22:09:47] but anyway its up
[22:09:55] http://drupal.org/node/1284300
[22:09:57] http://drupal.org/node/1284300 => Usability testing Drupal => 0 comments, 1 IRC mention
[22:10:16] clearly its incomplete, but wanted to give a picture, what I think the book how-to test could hold
[22:12:42] dcmistry, yoroy: let me know if we are thinking in the same direction
[22:14:29] Bojhan: I think those are the ingredients yes.
[22:15:05] getting consistent reports back would be a good thing, so a solid template for that would be nice
[22:15:15] yoroy: oh, yhea definitely
[22:15:41] yoroy: kind of the baltimore a-like reporting, I found that awesome
[22:15:53] needs some work structurally, a bit of intro etc. but overall
[22:15:55] good
[22:16:07] Bojhan: true, that report was a good read
[22:16:11] Bojhan: Yep, I think we do have all the important items in there.
[22:17:10] Bojhan: just wondering is it intentional that we have the tone to be casual than informational?
[22:17:23] dcmistry: err?
[22:17:42] dcmistry: where is that?
[22:17:53] Bojhan: just the tone of the overall guide
[22:18:04] Bojhan: it seems casual to me
[22:18:12] Bojhan: not sure what yoroy thinks
[22:18:14] dcmistry: guess it is then :)
[22:18:21] Bojhan: ha ha
[22:18:30] dcmistry: I dont know, just wanted to not make it sound like usability testing is heavy :)
[22:18:41] Personally, I have no problems with it.
[22:18:58] I was just wondering if it was intentional :)
[22:19:07] casual does not mean it's not informational?
[22:19:27] it needs an even more light-hearted intro imo
[22:19:44] yoroy: totally
[22:19:58] Bojhan, yoroy: Yep
[22:20:25] So, lets make a list of outstanding todo's for this guide?
[22:20:26] I think we need more info under "Testing"
[22:20:58] At the risk of making the guide lengthy, I say to invest on this because it is very important
[22:21:11] otherwise the research is not helpful :(
[22:21:13] dcmistry: lengthy should be oke
[22:21:22] Bojhan: Great!
[22:21:23] dcmistry: Aslong as it doesnt turn into a book :)
[22:21:44] lets move from top to bottom
[22:21:46] the intro
[22:21:52] Yes
[22:22:15] yoroy: any thoughts what should be in there? - anyone can test. - its easy, - reporting is key for action?
[22:22:21] the intro wants to make clear why testing is important and set expectations on that you can do it, too!
[22:22:30] yoroy: cool
[22:22:38] Bojhan is making a group comment with the notes
[22:23:06] I think when is done?
[22:23:07] yoroy, bojhan: agree
[22:23:09] Bojhan: yep! we need it for informed decisions, and although it def. takes some time, you can do it too.
[22:23:11] apart from dcmistry his edit?
[22:23:27] Bojhan: sorry, did not understand that?
[22:23:37] dcmistry: you had a minor edit on the wording of when not to test
[22:23:39] dcmistry: the part 'when to do"
[22:24:13] Bojhan: yep. we will do. Also "When to do usability testing?" … it has to be "What to test" "How many to test?"
[22:24:25] the Setup section might be called 'typical test scenario' or something, and made part of the 'Testing' section further down
[22:24:37] dcmistry: doesn't how many fit under setup?
[22:25:02] Bojhan noted what to test
[22:25:04] bojhan: yeah
[22:25:08] hmm, What to test
[22:25:12] yhea
[22:25:20] I think thats better?
[22:25:24] than when?
[22:25:52] When?
[22:25:54] There are no clues in there now that help people decide what to test
[22:26:08] or how to scope, define test tasks
[22:26:20] I am sorry things are crazy in the office today (so a bit pre-occupied)
[22:26:28] dcmistry: heh, no problem
[22:26:39] yoroy: I feel like that should be in setup
[22:26:55] I think the important questoins to be answered are:
[22:27:32] 1. What is the focus? What are the goals?
[22:27:32] 3. Why is it important?
[22:27:32] 4. What needs to be tested?
[22:27:32] 5. How do we test that?
[22:27:32] 6. How we choose the right participants?
[22:27:32] 8. Our planning document(s)
[22:27:33] 9. How do we conduct and analyze the results
[22:27:33] 12. How do we prioritise what needs to be fixed
[22:28:55] dcmistry: Hmm, arn't we at 5 now though?
[22:29:07] I mean overall
[22:29:13] the doc has to cover all these
[22:29:17] right
[22:29:19] not necessarily in the same order
[22:29:24] just putting it out there
[22:29:29] oh, heres my outline :) http://lullapad.com/Dcni0chafx
[22:29:48] Fantastic
[22:29:49] yoroy: hah
[22:30:04] yoroy: let me map those things in your outline
[22:30:05] one sec
[22:30:49] Guys, sorry but I will have to leave
[22:30:51] urgh :(
[22:31:02] but I am sure either of you would post the minutes
[22:31:09] sure
[22:31:14] I promise to give feedback and edit later
[22:31:16] bye
[22:31:21] thanks both of you
[22:31:51] yoroy: oke
[22:31:58] yoroy: mapped it!
[22:32:53] yoroy: I think the
[22:33:11] yoroy: focus, goals and why kind of emerge from the individual issues or discussions?
[22:36:42] Bojhan: yes
[22:37:09] I expect this doc to help those people who already have something in mind they want to test
[22:37:18] yoroy: right, m2
[22:37:31] ok
[22:38:32] yoroy: I have no idea how to give a generic answer to the "what to test" and "how to test" though
[22:39:35] yoroy: I have posted an updated comment post in your etherpad, I was going to post this on g.d.o does it look complete?
[22:40:12] Bojhan: 'What to test' : think of it as a scenario, a particular user journey or set of related tasks
[22:40:14] Bojhan: looking
[22:40:59] yoroy: hmm, thats more how, I think
[22:41:34] Bojhan: I can imagine that could help people scope out the 'what to test' too though
[22:41:57] some examples might work best here
[22:42:29] (not easy)
[22:44:20] yoroy: ahh ,yhea!
[22:44:29] yoroy: examples will be a good fit
[22:44:29] Bojhan: yeah 30 minutes total looks better :)
[22:44:38] yoroy: hah, a whole hour is scary :)
[22:44:45] true
[22:45:23] yoroy: ok, it looks good to post to me
[22:45:36] Bojhan: agreed
[22:46:07] Bojhan goes off to do the silly html part of the comment
[22:46:12] yoroy: want to take a stab at the intro?
[22:48:57] yoroy: pondering, whether a quick movie isnt better?
[22:49:13] guess, thats presentation, the text still has to be written heh