Attending: Colin, Daphne, Kris, Judy, Mara, Mike, Tim, OTHERS?
Please review carefully, these are pretty rough!
Activities for u-camps:
- Agreed again that we want to invite user-support and pedagogy people – they will bring (or send before hand) their top 5 issues (any information available in Jira would be great).
- Begin with an overview of working group activities (wg "lite") First half hour of day
- Brainstorm and reflection – what is our role, how do we become part of the development process, how do we make the UI activities more visible? [This activity seems out of the flow to me now --mh)
- Divide into groups and tackle the issues (3-4 person per team?)
- Workflow analysis (not sure how would do without users? pedagogy people?)
- Tool based vs. Task based flow
- Bring back to synthesize and present to stakeholders (Still need to determine the goal of doing this)
General Notes
Some Sakai stakeholders identified (not institutional):
- Chuck
- Peter Knoop
- Mark Norton
added by Mara afterward: - User Support teams
- Pedagogy team
- Developers
Kathy 
gave some feedback on experiences at WebCT –
Usability challenges eventually led to a complete development cycle overhall of UI – 1 release. How was that taken in the community? developers happy in general, but some crankiness when the rubber hit the road (difficulty implementing). Also, users had to relearn which is always an issue even if what they had was bad – this will happen with UI revision of any complex product. There was tons of workflow analysis at WebCT – people did use so differently that there wasn't a single workflow. Had to maximize for lots of activities...
Daphne that the Sakai UI doesn't have any particular relationship to user tasks across tools, it is more tool-centric.
TO DO
- Read the Mark Notess report (all)
- Send email out to user support / pedagogy groups (Mara)
- ichat or other VTC options? (Colin ask program cmte?)