Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Virtual Working Meeting (Toronto & Berkeley)

Monday, March 24:  10:30 PST (1:30 EST) - 4:00 PST (7:00 EST) (5 1/2 hours)

 1) Persona Pattern Exercise

  • Identify variables for continuums  (2 hours)
  • Place participants on the continuums (3 hours)
  • Identify Personas (1 hour)
  •  

Reference Material (from course management project):

Persona Scales:  http://bugs.sakaiproject.org/confluence/display/CM/Persona+Scales 

Course site structures, http://bugs.sakaiproject.org/confluence/display/CM/Course+and+Site+Structure+Patterns 

User Notes, http://bugs.sakaiproject.org/confluence/display/CM/User+Research 

Tuesday, March 25:  9:00 PST (12:00 EST) - 4:00 PST (7:00 EST) (7 hours)

1)  Create rough draft (whiteboard style) personas (2 hours)

2)  Use Case Identification  (2 hour)

  • Create high level categories
  • First stab at placing post-its on the board
  • Any gaps?

3)  Affinity Diagramming with use cases  (3 hours)

  • Grouping, categorizing, synthesizing, etc.
  • Create "parking lot" for non-content management use cases.  We'll share these out with the community but not do a lot of processing.

Monday, March 31:  9:00 PST (12:00 EST) - 4:00 PST (7:00 EST)  (7 hours)

1) Affinity Diagramming with use cases  (6 hours)

  • Grouping, categorizing, synthesizing, etc.
  • Document

2) Identify complex activities that require activity diagrams (1 hour)

  • Activity diagrams to be created later in pairs.

Tuesday, April 1st: 9-4 PDT/12-7 EDT

1) Mapping use cases to personas (2 hours)

2) Create use case priority matrix (5 hours)

  • frequency, importance and current user pain 

Wednesday, April 2nd: 1:30-4 PDT/4:30-7 EDT

1) Component ID & Prioritization (2 1/2 hours)

  • reassess current component priorities & fill in component gaps for 0.8 and 1.0 releases. 

To be scheduled

1)  Create activity diagrams identified above

2) Create list of context scenarios relevant to components on roadmap (requirements) 

3) Create rough outline of scenarios

4) Mental Model brainstorming 

  • No labels