Becca Scollan posted briefly here about a student project where they are considering doing some usability testing with Drupal at the University of Baltimore, which has the possibility to be expanded further in the summer. There are some preparation time constraints that at this point are leading her group to do consider completely replicating the scenario that was done at UMN, and it would be nice if some of the other admin test cases and tasks were fleshed out a bit more so that some new ground could be explored and to streamline the process a bit better.
There was talk at the UMN Usability session at Drupalcon that it would have been beneficial to set up the users with an initial "easy win" task that boosted their confidence -- like setting up an "About Us" page with a primary navigation link at the top. Webchick also pointed out that there were a number of task ideas that were discussed on this wiki page that were not executed, and that are still listed there with strikeout markup.
The intention of this wiki page is to flesh out some potential admin-related user scenarios that could be used now with this potential opportunity at the University of Baltimore. It could also serve as a general brainstorming place to flesh out other usability scenarios to be tested with other usability lab time as it becomes available.
Webchick mentioned that a big thing for them in creating the scenarios is that they wanted to make sure to avoid any "key words" that would help people clue in on what menu item to press. So instead of saying "Add a piece of workshop content", they say "Create a form for people to create workshops." So the tasks that we would normally describe in "Drupal" terms, need to be expressed in "human" terms since describing the tasks with the proper terminology would just become a game of keyword searching.
catch suggested the following things that weren't covered at UMN but might be interesting:
* menu module - both within node/add and the admin interface - there's a task for this but no-one got to it :)
* book module, taxonomy and forums (drag and drop, hierarchy, stuff like that).
* content administration - front page, sticky, published/unpublished/mass-updating
So if people here could help flesh out some specific tasks and ideal paths in the same format as listed here under the Site Maintainer Scenario & Tasks headings, then that would help out a lot