How Users Influence Design & Development

523 views

Published on

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.

Published in: Design
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
523
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
16
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

How Users Influence Design & Development

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

×