1. EVIA Digital Archive Iterative Development & Usability Testing Presented by William G. Cowan and Shahrier Akram Ethnographic Video for Instruction and Analysis Digital Archive Development Team DLP Brown Bag PresentationSeptember 26, 2007

2. Agile Software Development: Intro oCharacteristics of Agile Software Development Light-weight methodology Small to medium sized teams Vague and/or changing requirements Vague and/or changing technologies Simple design Minimal system into production Sep 26, 2007EVIADA : Iterative Design & Usability Testing

3. Agile Software Development : Intro oWhat Agile Software Development does not do: No complete up-front analysis No up-front infrastructure and framework Don’t write and maintain implementation documentation All programmers participate in all critical activities Sep 26, 2007EVIADA : Iterative Design & Usability Testing

4. Agile Software Development in EVIA oWhy Agile Software Development for EVIA? Shifting requirements Changing technology decisions Short development cycle with user review Keep focus on high priority items Small Development Team Daily review of progress Sep 26, 2007EVIADA : Iterative Design & Usability Testing

5. Usability in EVIADA Agile Software Development oHow can we incorporate some of the standard usability techniques into EVIADA’s Agile Software Development? Sep 26, 2007EVIADA : Iterative Design & Usability Testing

6. Rapid Contextual Design 1.Set project focus 2.Contextual Inquiry with potential customers 3.Build an affinity 4.Introduce data to the larger team 5.Identify issues 6.Build User Stories 7.Run the Planning Game 8.Design detailed User Interfaces (UIs) 9.Test UIs with users 10.Deliver to development 11.Continue iterations in parallel Sep 26, 2007EVIADA : Iterative Design & Usability Testing Beyer, H., K. Holtzblatt, et al. "An Agile User-Centered Method: Rapid Contextual Design.” Available at http://www.incontextdesign.com/resource/pdf/XPUniverse2004.pdf 1. Determine the complexity of the project and the level of innovation required. Identify the 1 or 2 key customer roles this product release will support and plan customer visits. 2. Gather data from at least 3 people in each Role to produce Affinity Notes and Sequence Models of as-is tasks. 3. Build the task models showing how specific tasks are currently done that which this project will support. This is a representation of the “as-is” customer work practice. 4. Summarize key findings, then walk the team through the affinity to allow the team members to comprehend the current customer environment. 5. Determine how the current issues will be addressed by the project. Brainstorm how to better support the work and develop sequence models 6. User stories guided by the sequence models will show how the system will resolve the issues 7. Organize these user stories into Iterations. Prioritize and eliminate stories as necessary to meet resource constraints. 8. Develop lo-fi paper prototypes 9. First round test with 3 to 4 users and use the results to refine design. Time permitting, do second round of tests with the refined design. 10. Provide the User Stories and the paper prototypes UIs to the development team for implementation 11. The UI Design Team begins work on the next Iteration. Turn over specs to Development team when they complete their current Iteration. Repeat steps 6 - 10 until project completion.

7. EVIADA Agile Usability oPick task(s) from Use Cases Inventory Prioritize tasks based on their critical need, anticipated frequency or commonality & complexity Sep 26, 2007EVIADA : Iterative Design & Usability Testing

8. EVIADA Agile Usability Contd. oCreate Descriptive User Stories Short Narrations, User Intentions & System Responsibilities, Sequence Models oRun the planning game with User Stories Detailed UI Mockups to determine the complexity and thereby time estimate to implement the features oTest Lo-Fi Paper Prototype of N Iteration Refine design Acceptance of N - 1 Iteration Refine design oContinue Design and Development Sep 26, 2007EVIADA : Iterative Design & Usability Testing

9. EVIADA: Iteration Turnaround Challenges oDeveloping unique task workflows User testing and feedbacks to validate concepts oAdopting new software technologies oUnforeseen technical roadblocks Cross-browser Incompatibilities oSequential design and development workflow Resource constraints Sep 26, 2007EVIADA : Iterative Design & Usability Testing

10. Usability Study oParticipants 2 Faculty 1 Graduate Student 2 General Public oTest Hi-Fi Prototype Video Playback Page (Iteration 1) Find relevant information based on user scenarios (In)validate currently implemented concepts Obtain qualitative, quantitative and informal feedbacks Demo Link oTest Lo-Fi Paper Prototype Browse Page (Iteration 2) Find information based on user scenarios (In)validate layout and labeling Obtain informal feedbacks Demo Link Sep 26, 2007EVIADA : Iterative Design & Usability Testing

11. Iteration 1 Usability Study: Qualitative Response oNegatives “ I was not aware if there was a page explaining some basics about scene, action, event and other aspects such as basic vocabulary” “The hierarchy of Collection, Event, Scene (& Action) wasn't spelled out very well in the interface” oPositives “After familiarizing myself with the interface I did not feel put off or frustrated” “LOTS of relevant information available about each segment I viewed” “Good use of color for displaying complex data” Sep 26, 2007EVIADA : Iterative Design & Usability Testing

12. Iteration 1 Usability Study - Quantitative Response Sep 26, 2007EVIADA : Iterative Design & Usability Testing Computer System Usability Questionnaire Overall, I am satisfied with how easy it is to use the system It was simple to use the system I can effectively complete my work using this system I am able to complete my work quickly using this system I am able to efficiently complete my work using this system …. Questionnaire available at: http://hcibib.org/perlman/question.cgi

13. Iteration 1: Pending Issues oConveying the segment hierarchy concept What are Collections, Events, Scenes & Actions? Alternative Approach: Sliding Drawer DemoSliding Drawer Demo o Mixed reception to the Interactive Visual Timeline Enhance level of interaction Sep 26, 2007EVIADA : Iterative Design & Usability Testing

14. Iteration 1: Development Status oEnhanced Video Player Full Screen Video Playback Player Reload vs Page Reload oImproved Collection Hierarchy Representation oCross-Browser Compatible oGraphic Design & Labeling Updates Aesthetics Visual Metaphors Labels oNew Features Transcriptions Technical Problems Glossary References Bibliographic References oDemo LinkDemo Link Sep 26, 2007EVIADA : Iterative Design & Usability Testing

15. Upcoming Objectives: oComplete Iteration 1 - Video Playback Page Do acceptance testing for the updates and enhancements Include students in the next usability study, if possible Incorporate feedback to refine design, if necessary oIteration 2 : Browse Page On hold oDevelop Design for Iteration 3 - Search Page Higher Priority Lo-Fi Paper Prototype Obtain feedback for proposed design Incorporate feedback to refine design, if necessary Sep 26, 2007EVIADA : Iterative Design & Usability Testing

16. Thank You! sakram@indiana.edu wgcowan@indiana.edu Special Thanks to: Mark Notess & The DLP Usability Working GroupThe DLP Usability Working Group Sep 26, 2007EVIADA : Iterative Design & Usability Testing Questions & Comments..