Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Panel

MeetingsUpcoming Meeting

Friday, May 25 - 8am PDT / 10am MDT / 11am EDT / 4pm GMT

Breeze: http://breeze.yorku.ca/fluidwork/

Previous meeting notes:   2007- May - 11 Meeting Agenda and Notes

User Experience Inspections of uPortal, Moodle, Sakai

(Usability and accessibility Heuristic Evaluationsand Cognitive Walkthroughs)

...

The working list of heuristics and cognitive walk-through questions for the Fluid project is being compiled at the User Experience Inspection wiki page. We welcome your input, and would very much appreciate additional volunteers to help with the evaluation process.

User Experience Inspection Protocol / Checklist

The checklist is organic and will continue to be refined as we learn from doing the hybrid evaluations.

"To Do" list - User Experience Inspection Protocol

As a group: 

  1. DONE - Create list of usabilty accessibility heuristics - use draft list to get started.  In the spirit of agile, we'll refactor the list as we learn from the experience of combining the usability and accesibiliy heuristics and the cognitive walkthrough methods
  2. Agree on evaluation reporting format

Within the "application" teams:

  1. Agree on user profiles

Evaluation Process (draft)

Assumptions:  Protocol has been created

  1. Break application into "chunks" for evaluation (highest priority areas first)
  2. Create usage scenarios for cognitive walkthroughs
  3. Individual evaluation by 3 - 5 evaluators
  4. Synthesize and prioritize findings
  5. Brainstorm design session (identify conceptual solutions to high priority issues).  Are there good component candidates?
  6. Write and share out report
  7. Incorporate findings into community (some will drive component development - others can be used for general product development in the communities)
    1. Sakai - Integrate into requirements group.  Do we need to create jira tickets?  Are these really "design bugs" conceptually and thus have a different status than requirements?
    2. Moodle - how does this get fed back into the process?
    3. uPortal - how do we integrate into their requirements process?  Deliver findings to the community?
  8. Look for pain across applications? Are there issues a component(s) can address well?

User Experience Inspection

Heuristic evaluation & Cognitive walkthrough reference material:

Jacob Nielsen'sdescription and overview
Applying Heuristics to Perform a Rigorous Accessibility Inspection in a Commercial Context 

...