How Users Influence Design & Development
Upcoming SlideShare
Loading in...5
×
 

How Users Influence Design & Development

on

  • 931 views

A talk about how Stanford's team organizes itself and communicates for local and community development. Discussed both intra and intercampus communication in an effort to solicit ideas for ...

A talk about how Stanford's team organizes itself and communicates for local and community development. Discussed both intra and intercampus communication in an effort to solicit ideas for generalizable best practice.

Statistics

Views

Total Views
931
Views on SlideShare
930
Embed Views
1

Actions

Likes
0
Downloads
14
Comments
0

1 Embed 1

http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

How Users Influence Design & Development How Users Influence Design & Development Presentation Transcript

  • How Users Can Influence Design & Development
    Keli Amann, Stanford University
    User Experience Specialist, kamann at stanford.edu
  • User Experience
    Developers
    Keli Amann
    UX Specialist
    Lydia Li
    Developer
    Makoto Tsuchitani
    Director
    Christine Doherty
    Support
    Karen Tsao
    Developer
    Jasmine Thapa
    QA
    Jackie Mai
    UX Specialist
    Jing Wei
    Developer
    Julian Morley
    Sys Admin
    Who we are
  • Why the title is misleading
    “How Users Can
    Influence Design & Development”
    How Do We Organize and Communicate
    Among Ourselves so that Users Can
    Influence Design & Development”
  • Patterns of communication
    ?
    Dev?
    Dev
    ?
    UX?
    UX
    ?
    Users
    Users
    within campus
    • between campuses
    • during different types of development
  • …during different types of development?
    Local Quarterly Updates
    • 2.x releases of Tests & Quizzes (SAMigo)
    • Major Revisions
    Dev?
    Dev
    ?
    UX
    UX?
    Users
    Users
  • Why talk about how we communicate?
    We have assumptions about how others work and what they know. Are these correct?
    We have methods to communicate issues. Are these methods always the best?
  • Engaging the issues: Two styles
    A Basketball Analogy
    July 2009
    10th Sakai Conference - Boston, MA, U.S.A.
    7
  • T&Q
    Announcements
    Resources
    Pilot Tools
    Local Tools
    Zone Defense
  • T&Q
    Announcements
    Pilot Tools
    Resources
    Man to Man Defense
    Not 1:1
  • What style do you use?
    Do you take care of
    only local issues?
    only community issues?
    Both local and community issues?
    We use both styles, and it depends on the type of development
  • Part 1
    Local Quarterly Updates
    July 2009
    10th Sakai Conference - Boston, MA, U.S.A.
    11
  • UX
    Users in 7 schools
    1600 instructors
    18,000 students
    What UX does locally
  • Schedule for Local Quarterly Updates
    Su release
    Fall release
    Win release
    Sp release
    UX
    Dev
    QA
    Op
    prioritization
    UX
    Dev
    QA
    Op
    prioritization
    UX
    Dev
    QA
    Op
    prioritization
    UX
    Dev
    QA
    Op
    prioritization
    |September |October|November|December|January|February|March |April |May |June |July | August |
  • QA
    Local JIRA
    Dev
    Sakai JIRA
    conversation
    survey
    questionnaire
    ticket
    Workflow for Local Quarterly Updates
    UX
    Users
  • Local updates at your school
    conversation
    survey
    questionnaire
    ticket
    Who interacts with users at your school?
    How do they solicit user input & prioritize?
    Who are users needs communicated to? How?
    Local JIRA
    Dev
    Dev
    Sakai JIRA
    UX
    UX
    Users
    Users
  • Process 2
    2.x releases
    July 2009
    10th Sakai Conference - Boston, MA, U.S.A.
    16
  • Schedule for 2.6 release (in production 2010)
    2.6
    2.6 localization
    prioritization
    Dev codes, releases Alpha
    Beta
    Release Cand
    QA
    Op
    UX reviews locally
    Dev tweaks..
    |September |October|November|December|January|February|March |April |May |June |July | August |
  • Workflow for 2.6 Tests & Quizzes
    Dev
    UX
    Dev
    Whatever was finished by Oct 2008
    Code from previous local quarterly release
    Code contributed by UPV, Rutgers, Capetown, reinforced by email, dev list
    If feature request had no assignee, developers didn’t see
  • New/Old workflow for 2.x
    Local JIRA
    Sakai JIRA
    UX
    Dev
    Dev
    What are we looking for
    • Context that explains wide impact
    • Votes/Watches
    • Personal relationship
  • 2.x work at your school
    Do you solicit/review external feature requests?
    How are requests communicated to you?
    Who manages community requests? How prioritize work?
    Dev
    Dev
    Sakai JIRA
    UX
    UX/ID/Support
    Users
    Users
  • Process 3
    Major revision of a tool
    July 2009
    10th Sakai Conference - Boston, MA, U.S.A.
    21
  • What’s a major revision?
    SAMigo designed in 2005
    • Many functional updates
    • No major interface change since
    “SAMigo 3” (not necessarily 3akai)
    • Limited functional update
    • Redesign screens, interaction styles, & workflow
    Holistic redesign: not collecting new JIRA features
  • Workflow for a major revision
    history
    history
    Dev
    Dev
    plan
    UX
    UX
    Plan = Motivation, Use cases, Timeline
  • An additional step
    We’ll want to create
    • Vivid descriptions of users and their needs
    • Rich realistic scenarios
    To be successful, design must hold up to a walkthrough of vetted scenarios
  • Ideal workflow for a major release
    history
    history
    Dev
    Dev
    plan
    UX
    UX
    Users
    Users
    Users
    Plan = Motivation, Use cases, Timeline
    + persona description, scenarios
    Use cases/ scenarios via Confluence
    Interview,
    Questionnaire
  • Making SAMigo 3 fit into this kind of schedule
    prioritization
    Dev codes, releases Alpha
    Beta
    Release Cand
    QA
    UX
    Dev
    Op
    QA
    Op
    prioritization
    UX reviews locally
    UX
    Dev
    QA
    Dev tweaks..
    Op
    prioritization
    UX
    Dev
    QA
    Op
    prioritization
    UX
    Dev
    QA
    Op
    prioritization
    |September |October|November|December|January|February|March |April |May |June |July | August |
  • Questions about this approach
    Do you have someone who can collect stories?
    Do want our stories about your tools, or just JIRA?
    What else do you recommend to insure success?
    Dev
    Dev
    Sakai JIRA
    UX
    UX? ID? Support?
    Users
    Users
  • Final thoughts
    We can succeed at our schools, but we have to succeed as a team.
    JIRA is necessary and valuable
    Interpersonal communication enhances and complements JIRA
    Speaking of which…
  • Continuing the conversation
    • Questionnaire: will email results
    • Birds of a Feather
    • Confluence page
    • Contact me kamann at stanford.edu
    • Talk now…
  • Your thoughts
    How are you facilitating communication
    • With your users?
    • Within your team?
    • Between schools?