powerpoint presentation - iterative development

EVIA Digital Archive

Iterative Development & Usability Testing

Presented by William G. Cowan and Shahrier AkramEthnographic Video for Instruction and Analysis Digital Archive

Development Team

DLP Brown Bag Presentation September 26, 2007

Agile Software Development: Intro

o Characteristics 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

Agile Software Development : Intro

o What 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


Agile Software Development in EVIA

o Why 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


Usability in EVIADA Agile Software Development

o How can we incorporate some of the standard usability techniques into EVIADA’s Agile Software Development?


Rapid Contextual Design1. 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


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 eachRole to produce Affinity Notes and SequenceModels of as-is tasks.

3. Build the task models showing how specifictasks are currently done that which this project will support. This is a representationof the “as-is” customer work practice.

4. Summarize key findings, then walk the teamthrough 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 sequencemodels

6. User stories guided by the sequence modelswill show how the system will resolve the issues

7. Organize these user stories into Iterations.Prioritize and eliminate stories as necessaryto meet resource constraints. 8. Develop lo-fi paper prototypes9. 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 teamfor implementation

11. The UI Design Team begins work on thenext Iteration. Turn over specs to Development team when they complete their current Iteration. Repeat steps 6 - 10 until project completion.

EVIADA Agile Usability

o Pick task(s) from Use Cases Inventory• Prioritize tasks based on their critical need, anticipated frequency or commonality &

complexity


EVIADA Agile Usability Contd.

o Create Descriptive User Stories• Short Narrations, User Intentions & System Responsibilities, Sequence Models

o Run the planning game with User Stories• Detailed UI Mockups to determine the complexity and thereby time estimate to

implement the features

o Test• Lo-Fi Paper Prototype of N Iteration

• Refine design

• Acceptance of N - 1 Iteration• Refine design

o Continue Design and Development


EVIADA: Iteration Turnaround Challenges

o Developing unique task workflows• User testing and feedbacks to validate concepts

o Adopting new software technologies

o Unforeseen technical roadblocks• Cross-browser Incompatibilities

o Sequential design and development workflow• Resource constraints


Usability Study

o Participants• 2 Faculty• 1 Graduate Student• 2 General Public

o Test 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

o Test Lo-Fi Paper Prototype Browse Page (Iteration 2)• Find information based on user scenarios• (In)validate layout and labeling• Obtain informal feedbacks• Demo Link


Iteration 1 Usability Study: Qualitative Response

o Negatives• “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”

o Positives• “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”


Iteration 1 Usability Study - Quantitative Response


0

1

2

3

4

5

6

7

8

Overall, I am satisfied with how easy it is to use this system

It was simple to use this system

I can effectively complete my work using this systemI am able to complete my work quickly using this system

I am able to to efficiently complete my work using this system

I feel comfortable using this systemIt was easy to learn to use this system

I believe I became productive quickly using this system

The system gives error messages that clearly tell me how to fix pr...Whenever I make a mistake using the system, I recover easily and ...The information (such as online help, on-screen messages, and othe...

It is easy to find the information I needed

The information provided for the system is easy to understand

The information is effective in helping me complete the tasks and s...

The organization of information on the system screens is clear

The interface of this system is pleasantI like using the interface of this system

This system has all the functions and capabilities I expect it to have

Overall, I am satisfied with this system

Questions

Ratings

Average Rating (0-7)

Computer System Usability Questionnaire

Computer System Usability Questionnaire

• Overall, I am satisfied with howeasy 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 workquickly using this system• I am able to efficiently completemy work using this system• ….

Questionnaire available at:http://hcibib.org/perlman/question.cgi

Iteration 1: Pending Issues

o Conveying the segment hierarchy concept• What are Collections, Events, Scenes & Actions?• Alternative Approach: Sliding Drawer Demo

o Mixed reception to the Interactive Visual Timeline• Enhance level of interaction


Iteration 1: Development Status

o Enhanced Video Player• Full Screen Video Playback• Player Reload vs Page Reload

o Improved Collection Hierarchy Representation

o Cross-Browser Compatible

o Graphic Design & Labeling Updates • Aesthetics • Visual Metaphors• Labels

o New Features• Transcriptions• Technical Problems• Glossary References• Bibliographic References

o Demo Link


Upcoming Objectives:

o Complete 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

o Iteration 2 : Browse Page• On hold

o Develop Design for Iteration 3 - Search Page• Higher Priority• Lo-Fi Paper Prototype• Obtain feedback for proposed design

• Incorporate feedback to refine design, if necessary


Thank [email protected]

[email protected]

Special Thanks to:

Mark Notess & The DLP Usability Working Group


Questions & Comments ..

powerpoint presentation - iterative development

Documents