Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

22 Apr 2010, 11:30am - 1pm Eastern, Sakai001 Conference Bridge (+1-812-856-7060/156.56.240.9##22X, Code: 22348#, PIN: 72524#)

Info

We'll be using Breeze to present slides for this meeting at: http://breeze.iu.edu/libsakai

Where We Are

The Data Analysis Group has:

  • created four instructor personas based on data from our user study - view the personas
  • added details to our workflow data based on additional feedback from users
  • developed a collaborative activity to build context scenarios to arrive at requirements

Agenda

  1. Introductions
  2. Sharing Personas
  3. Sharing additional details gathered about Workflows
  4. Proposing a Collaborative Context Scenarios Activity for the community to participate in
  5. Next steps

Meeting Notes

In attendance

Name

Institution

Debra Kolah

Rice University

Leah Krevit

Rice University

Val Moule

Naval Postgraduate School

Chris Strauber

Tufts University

Jim Martino

Johns Hopkins University

Jennifer Vinopal

New York University

Daphne Ogle

UC Berkeley

Kalee Sprague

Yale University

Keli Amman

Stanford University

Carrie Donovan

Indiana University

Mark Notess

Indiana University

Jon Dunn

Indiana University

Gaurav Bhatnagar

University of Michigan

Sorry for any misspellings or omissions! Please feel free to edit the table above or send Gaurav a message if you do not have a wiki account.

Summary

Thanks to everyone who was able to make it to our web meeting! There was a lot of material to cover and we focused mainly on discussing personas. We touched briefly on additional workflow information and the collaborative context scenarios activity. We will be working together over the coming weeks to move forward with creating context scenarios based on our personas and workflow data. For our next web meeting on 27 May, we aim to share design requirements based on our context scenarios as well as some initial low-fidelity prototypes. Our conference proposal has been accepted and we will be summarizing the work we have done thus far at the Denver Sakai conference on 15-17 June. More details from our meeting are outlined below.

Personas

Personas help reduce the complexity of all our actual user data while allowing the project team to communicate with the goals and behaviors of our end users in mind. As the project gets closer to being released, personas also help in building stronger marketing materials that make the final product more compelling for the end user.

The three personas (Juanita, Vijay and Cynthia) were generally well received. They are good depictions of real life instructors and have broad coverage across instructor types. There are some areas which we need to clarify and add more detail:

  • relationship with the library - how are (or, are not) instructors interacting with the library?
  • diversity of content selection criteria - what are the variety of things instructors are looking for when selecting resources?
  • managing content - particularly different tools they may be using; i.e. Zotero, RefWorks, etc.
  • sharing content - how are instructors eventually sharing content and getting feedback on what they have shared?

The data analysis group will be expanding our personas to add more details in the above areas. The fourth persona, Ronald Moore, a professor in government affairs that teaches online distance courses through Sakai, will be finished and shared soon.

Workflow

The data analysis group has received additional details from interviewees on their workflow. Our focus is the cycle of finding, managing, sharing and evaluating resources for teaching and learning. Analyzing and summarizing the additional workflow information is still happening. A summary of all workflow data will be shared soon to help inform writing context scenarios.

Collaborative Context Scenarios Activity

Context scenarios allow us to put ourselves in the shoes of our personas by describing real-life, ideal experiences they would expect from our design. It allows the design team to come up with "outside the box" solutions and discover gaps that they have not previously considered. Iterating through context scenarios help us arrive at user-centered requirements for the design.

The collaborative context scenarios activity allows members of the community to contribute context scenarios for our design. The process consists of:

  1. Understanding the personas
  2. Understanding the workflow summary
  3. Understanding the overall design's problem and vision statements
  4. Choosing a persona and an activity to detail in a context scenario
  5. Writing the context scenario
  6. Reflecting on the context scenario

More details on how to participate in the collaborative context scenarios activity will be coming soon.

Next Steps

  • Apr 22 to May 27
    • Collaborative context scenarios activity
  • For our May 27 web meeting
    • Context Scenarios: Present a summary of the context scenarios developed and derived requirements.
    • Initial design prototypes: Present initial design prototypes based on context scenarios and requirements.
  • May 27 to Mid-June
    • Collect user feedback on initial design prototypes
    • Prepare Sakai Conference presentation
  • June 15
    • Present initial designs at Sakai Conference (our proposal has been accepted!)