Re: [GMG-Devel] Proposed UX workflow

[Christopher Allan Webber]

Hi Christian,

Useful feedback, thanks!  Could you possibly expand on or at least dump
these in here:

http://wiki.mediagoblin.org/User_Experience#General_thoughts_on_running_a_user_experience_test

Thanks!  Your feedback is appreciated! :)
 - Chris


Christian Baumann <address@hidden> writes:

> Hi all,
>
> some ideas on testing:
> #1 List new features, so testers now where to concentrate on.
> #2 Define list of "have to work to be releasable"-features, so testers now 
> where to concentrate on.
> (#3 Update #2 based upon #1 after each release)
> #4 Try to set up automated tests for #2
> #5 Ensure documentation is up to date, so testers now how to software is 
> intended to use
> #6 List some standard workflows, with defined inputs and expected outputs.
>
> Regards,
> Christian
>
> 2011/8/22 Deborah Nicholson <address@hidden>
>
>     Hi all,
>     I've been doing some thinking and some research into how we might best
>     carry out UX testing for MediaGoblin. If you have thoughts on this
>     process, I'd love to hear them.
>    
>     My goals for the process are:
>     1. Make it easy for testers, so we can test often.
>     2. Do our best to not color their responses, despite the fact that
>     many testers may be friends or colleagues.
>     3. Make sure feedback goes back into the project.
>     4. Keep it cheap, at least for now.
>    
>     Based on those goals, here's my proposed workflow:
>    
>     1. For each planned release set up an instance for users to test. I
>     think about ten days before the monthly development meeting would work
>     well. Give users one week to play around, do mission-based tasks and
>     schedule a handful of remote desktop sessions where we watch them use
>     the site. For now, I'm happy to do the watching myself. All feedback
>     goes on that version's wiki page.
>    
>     2. Triage those comments and make tickets for the things we want to
>     change/add/fix. Maybe this is addressed in the monthly dev meeting?
>     Link those tickets to the wiki page.
>    
>     3. Make a new page for the next version. Repeat! (And profit!)
>    
>     Cheers,
>     Deb
>     _______________________________________________
>     devel mailing list
>     address@hidden
>     http://lists.mediagoblin.org/listinfo/devel
>
> --
> Christian Baumann
> Schliezgasse 29 | D-54636 Bitburg
> Phone: +49 (0) 65 61 / 69 40 52 7 | Mobile: +49 (0) 17 1 / 70 07 97 5
> http://agile-and-testing.chriss-baumann.de/ | http://blog.chriss-baumann.de | 
> http://pepes-bigband.de
>
> _______________________________________________
> devel mailing list
> address@hidden
> http://lists.mediagoblin.org/listinfo/devel

-- 
𝓒𝓱𝓻𝓲𝓼𝓽𝓸𝓹𝓱𝓮𝓻 𝓐𝓵𝓵𝓪𝓷 𝓦𝓮𝓫𝓫𝓮𝓻