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.

1. How Users Can Influence Design & Development Keli Amann, Stanford University User Experience Specialist, kamann at stanford.edu

2. 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

3. 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”

6. Major RevisionsDev? Dev ? UX UX? Users Users

7. 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?

8. Engaging the issues: Two styles A Basketball Analogy July 2009 10th Sakai Conference - Boston, MA, U.S.A. 7

9. T&Q Announcements Resources Pilot Tools Local Tools Zone Defense

10. T&Q Announcements Pilot Tools Resources Man to Man Defense Not 1:1

11. 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

12. Part 1 Local Quarterly Updates July 2009 10th Sakai Conference - Boston, MA, U.S.A. 11

13. UX Users in 7 schools 1600 instructors 18,000 students What UX does locally

14. 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 |

15. QA Local JIRA Dev Sakai JIRA conversation survey questionnaire ticket Workflow for Local Quarterly Updates UX Users

16. 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

17. Process 2 2.x releases July 2009 10th Sakai Conference - Boston, MA, U.S.A. 16

18. 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 |

19. 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

21. Votes/Watches

23. Process 3 Major revision of a tool July 2009 10th Sakai Conference - Boston, MA, U.S.A. 21

26. Redesign screens, interaction styles, & workflowHolistic redesign: not collecting new JIRA features

27. Workflow for a major revision history history Dev Dev plan UX UX Plan = Motivation, Use cases, Timeline

29. Rich realistic scenariosTo be successful, design must hold up to a walkthrough of vetted scenarios

30. 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

31. 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 |

32. 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

33. 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…

35. Birds of a Feather

36. Confluence page

37. Contact me kamann at stanford.edu

39. Within your team?

40. Between schools?