• The team decided to have the following roles at the team of 9 level:
  • Project Manager – Ryan
  • Project Coordinator/POC – Sally
  • Workspace Manager – Sue Dass
  • Webmaster – Debra
  • Scribe – James
• Roles at the Team of 9 level will rotate every 5 weeks following the syllabus phases on:
  • January 19 – February 18
  • February 19 – April 1
  • April 2 – May 6
• Final Deliverable Report roles will be defined as the date approaches; some considerations will include section editors, document editor, quality assurances; writers of Executive Summary etc.
• Individual teams of three will have a leader, scribe, and liaison.  Roles will rotate as decided by each team

2. Project Structure

• We discussed the breakout of the three teams; we think it is the best structure
• The team emphasized the importance of lateral communication; each team is responsible for the “design” of their component, but content must be provided by the individual who did the research on it
• We need to evaluate if there is a better way – maybe we could have two teams who work on the resource and decision component and then three teams who develop best practices
  • Need to verify deadlines; see if we can push the schedule forward

3. Assign Readings

• James will make a schedule; teams will rotate weekly on the responsibility of leading reading discussions.

4. ACQ 201A/B

• Sally will email Nada about getting design document for both courses as well as getting amplifying information about what DAU wants us to look at with 201B.

5. Workshops

• Everyone consider technologies we would like workshops on.  Sue Dass will put list on Wiki and the team will rate their preferences at that time.

6. ID Panel

• Everyone consider ID panel – Sectors and businesses we may want to come and talk to us about ISD in the workforce

7. Revisit Team Norms

• We reviewed team norms and feel they are still relevant and do not require any changes

8. Team Goals

• Review team goals
• Consider personal goals; be prepared to discuss new team goals

9. Google Calendar

• Major deliverables are posted on Google Calendar
• Calendar will be shared; not edit access – only PM has edit access
• Shantell will do functionality testing on Google Calendar and report back to team

10. Timeline/Schedule

• We should begin working on our wireframes as soon as possible
• Need to speak with Kevin and Nada; what should we have before our meeting with the developers? What are we getting out of our meeting with the developers?
• Get clarification on schedule/deliverables

11. Wednesday Meetings

• Each team will be allotted time to discuss what their team is doing
• Each team will have “individual team” minutes to be consolidated into “team of 9” minutes