We are taking a parallel approach to design and development. UX will focus on requirements, interaction and interface for what is mostly existing backend functionality in Sakai 3 now: Creating & managing membership in manually created groupswhile the development will support creating a prototype for this work and look forward to service capabilities we'll need around course management and external group provisioning. This approach will allow us to move forward with a short term goal and still be moving toward the bigger picture. We expect it will also allow us to uncover and work through challenges in the more simple space of manually managed groups before jumping into complicated areas.

Note: We will naturally be gathering requirements for the bigger picture while focused on the this initial phase.

Time line

The below time line is meant to provide a framework for project planning. It is not intended to outline a commitment to deliver any single set of capabilities according to a predetermined series of fixed dates. The time line does represent approximate dates by which the delivery of major pieces of working code must be integrated with K2 and/or 3akai in order to mark essential progress for the project and, in all likelihood, Sakai 3.0 as whole.

	Milestone	Date
1.	Design and develop initial prototype based on existing use cases (phase 1)	September 2009
2.	User test prototype	October 2009
4.	Integrate findings, additional use cases into design and development iteration.	November 2009
5.	Test prototype/QA	December 2009
6.	Integrate pilot experience/feedback into next design and development iteration	May 2010
7.	QA	June 2010

Phase 1 Scope

Phase 1 is scheduled through the end of September 2009 (see above). Within each phase we will take an iterative approach to design and development to allow us to be flexible and collaborative with related work on Sakai 3.

Define group
Add & drop members
View membership
Find groups
Choose groups
Manage member default abilities

Out of scope:

Interacting with and referencing groups from contexts outside the context we originally build in (i.e. send email)
- We need to understand how these are referenced in order to understand needs
- We may also create design patterns that enable holistic design across Sakai

Activities For September 2009 - Phase 1

User Experience

Focus on creating & managing membership in manually created groups
- Gather use cases and scenarios - defining the space
- Gather collaborators & build community
- Benchmarking & exploring user's existing mental models
- Activity Models: activity diagrams, context scenarios
- Design: Wireframes, paper prototype user testing

UX Activities (groups) detailed task list

Development

Focus on creating & managing membership in manually created groups
- Build prototype going against K2 - iterating on K2 to meet user stories
Service capabilities exploration: exposure to external groups & roles

Project Management

Prioritization of core use cases
alignment with Sakai 3 projects
Recruitment of a "community of project participants"

Groups

Group Project Plan