Story Cards

Design Story Cards

• May 8-12, 2006
  • Define design process story cards (4)
  • Summarize user interviews and observations (4)
    • Use whiteboard exercise to cull information from interviews and observations
• May 15-19, 2006
  • Finish summarizing user interviews and observations (4)
    • Use whiteboard exercise to cull information from interviews and observations
  • Create a document (set of whiteboards) that outlines the high-level finding for each including these categories fore each person include:
    • General (goals, typical/good/bad day, etc.)
    • Site set-up
    • Content
    • Sections
  • Persona differentiation scales (8)
    • Define the different factors
    • Assign interviewees to each scale
    • Discern patters/groupings for personas
    • Write a short title/name for each variable
  • Create draft personas each patten (8)
    • title and picture
    • 3-4 goals
    • paragraph description (typical day, problems with current solutions, work environment)
    • where they fell on each variable in scales
  • Conference presentation prep (4)
• May 22-26, 2006
  • Persona mapping activity (1)
    • Choose primary persona
    • Create persona map and talk through primary and secondary persona options
    • Choose primary and secondary personas
  • Iterate on personas (2)
    • Do we have the whole persona set?
    • Flesh out primary and secondary personas
    • Tighten up description and goals
  • Mental model exercise (4)
    • Using Cooper exercise, flesh out users' existing mental models
    • For each model, define user expectations for new product based on their models
  • Create context scenarios (10)
    • Brainstorm context scenario concepts using title/build on current list
    • Assume ten context scenarios
    • Describe each context scenario step-by-step using bullet points
  • Brainstorm design ideas (4)
    • Using whiteboard, brainstorm and capture current design idea
    • The idea is to get all these ideas out to forget about them for now
  • Conference presentation prep (4)
• June 12-16, 2006
  • Define data needs, functional needs and general considerations (4)
    • Using Cooper process, pull data needs, functional needs and general considerations from context scenarios, user goals and mental models
    • Create information matrix (Cooper slide 100)
  • Merge requirements into one document (6)
    • Add sub-functions to current Sakai function list
    • Finish chunking original requirements document into functional areas
    • Add user research-based requirements
    • Locate existing requirements not covered in new design
  • List functional and data elements base on needs (4)
    • Define data elements (basid data units that fit the mental model)
      • Does not include attribute (smallest pieces of data e.g. DB fields)
    • Define functional elements for the functional needs (tools that act upon data objects)
    • Use Cooper matrix to track
  • Group elements and determine hierarchy (2)
    • Determine a hierarchy of functional elements
    • Group elements in the most appropriate ways based on sequence of use
    • Foundation of sketches
    • Break out by tool
  • Turn context scenarios into key path scenarios (4)
    • Incorporate functional and data elements into scenario
    • Key path scenarios describe the persona's most important or frequent workflows, using the interaction framework
    • Assume 3 or 4
• June 19-23, 2006
  • Sketch the framework (4)
    • Define the views (see Cooper day 4, slide 31)
      • Number of views often equals the number of context scenarios
    • Draw rough outline of each view
    • Lay out panes within each view, give them names and definition and discuss the relationships among them
      • Whatever gets used first goes toward the top and left
      • See day 4, slide 36
    • Determine how the views and panes affect each other (dee day 4, slide 39)
    • AVOID DOING THE DETAILS YET!
  • Check the framework design with the validations scenarios (2)
    • Check for scenarios outside the key path scenarios (not edge cases, but fairly common circumstances)
    • Be sure to look at secondary personas here, these are the "what-ifs"
  • Iterate on conceptual framework (2)
    • Add more detail to critical path scenarios
    • Add in some widget detail (what they are, not how they work)
• June 26-30, 2006
  • Flush out details of a design for a context scenario
    • Based on 2nd iteration of conceptual framework, flesh out details of interaction
    • Work should be at the widget and attribute level
    • Artifacts are wireframes to pass of to development
    • Include details of interaction elements (functional specs)
  • Manually create course site (8)
  • Request (instructor) and approve (support staff) course site (8)
• July 3-7, 2006
  • Automatically create course sites (8)
  • Manually add people to my site and assign them to sections (if applicable) (8)
• July 10-14, 2006
  • Students sign-up for sections (already in course, no SIS data for sections) (8)
  • Automatically add students to my site (8)
• July 17-22, 2006
  • Manually manage sections previously managed automatically (8)
  • Manually create sections for my course site (8)
• July 24-29, 2006
  • Reuse material from previous site (8)

Development Story Cards

Research Inter-Tool Linking
Research Inter-Site Linking
Schedule Object For AcademicSessions, CourseOfferings and CourseSections