Agenda:

Scope
- Notes from Tuesdays Scoping Meeting: http://confluence.sakaiproject.org/display/GROUPS/Groups+Priorities+Meeting+-+8-11-09;jsessionid=3E16677626CD0BCFCE952748DCB425C2
Group type matrix: http://spreadsheets.google.com/ccc?key=rXb1dLcREdpWX5hUm2INCnQ&hl=en
Context Scenarios: http://confluence.sakaiproject.org/pages/viewpage.action?pageId=16220197
UX Activities: http://confluence.sakaiproject.org/display/GROUPS/UX+Activities+(groups)

Notes:

Discussed current thinking around scope:

Creating groups within the context of a site is the 50,000 view. More details and specific use cases will be shared soon.

Group functionality supported in current implementation

1) Interest groups - (throw-away experimental code here)- Academic interests - search people for interests > create a research site (and implicitly group) ***related to Shared interests, attributes category or scenarios

2) adding individuals to site - via cvs file or searching for people already known in the system.

Group Type Matrix - meant to help us get us understand this space. It represents concrete examples of types of groups, how those groups get created, who is involved, typical interactions, etc.
- we need to be able to tie this back to the use cases and scenarios. They give us fodder for both.
- admitted students are an important group. reaching out to students early so that they become a part of the community, get a sense of what it will be like to go to school there, want to go to school there.
**At Berkeley, Facebook is being used for this purpose. Would it be better to have this happen in the CLE/LMS?

UX Activities:
- Reviewed confluence page
- 1st iteration was about capturing what we know about groups, making sense of it and putting into forms we can work with (group types spreadsheet, use case matrix, scenarios, etc.)
- 2nd iteration is focused on benchmarking and documenting a wide range of context scenarios around creating groups and adding members to groups.
- 3rd iteration is design studio which is kick off for wirferaming.
- By 4th iteration we hope to be doing paper prototype user testing and beginning to build the working prototype.
- 5th iteration we'll add visual design while continuing prototype building
- 6th iteration more prototype building along with identifying design patterns in our work and documenting them to share with community.
- 7th iteration is more in depth user testing with the working prototype- 8th iteration is changes based on testing results

- Using agile process so all of this is subject to change. We reflect and reevalaute what is needed based on where we're at and what we've learned in the past iteration.

Context Scenarios
The core of design. These concrete stories about users completing activities will be the drivers for our design work. We will design to and for them.
- Doesn't need to be a comprehensive set but rather a representative set. We'll choose a handful to begin designing for and use the rest as test cases as design progresses.
- They should tie back to the use cases
- The group type spreadsheet should give us a lot of fodder for these along with the various places we've been pulling information from already (see UX activitites page)
- Would like help building these out. This week we'll keep it to those on the call and working on group management on a day to day basis. Once we have a good representation, we can open it up to the community for feedback and to fill in gaps.

To DOs:

- Send email about adding context scenarios - Daphne
- Add context scenario about implicit groups - searching for people with particular interests that you turn into a group (or not) - Daphne
- Add context scenario about informal group that grows over time - Keli
- Add context scenarios about creating & using groups in the context of communication (likely email) - Berkeley
- Start agenda page for next week's meeting we can build together