Agile Usability Testing Methods

Slides:



Advertisements
Similar presentations
Overview of the Interaction Design Process. Objectives By the end of today’s class you will be able to… –Describe the major steps in the interaction design.
Advertisements

PROC-1 3. Software Process. PROC-2 What’s a process? Set of activities in creating software It involves creativity –hard to automate –Requires human judgment.
Chapter 05: Evolutionary Requirements Definition : Requirements  “Requirements are capabilities and conditions to which the system, and more broadly.
CS305: HCI in SW Development Evaluation (Return to…)
Agile 101.
Alternate Software Development Methodologies
Each individual person is working on a GUI subset. The goal is for you to create screens for three specific tasks your user will do from your GUI Project.
WHAT IS INTERACTION DESIGN?
Saul Greenberg User Centered Design Why User Centered Design is important Approaches to User Centered Design.
Part 1: Introducing User Interface Design Chapter 1: Introduction –Why the User Interface Matters –Computers are Ubiquitous –The Importance of Good User.
Methodology Overview Dr. Saul Greenberg John Kelleher.
James Tam User Centered Design Why User Centered Design is important Approaches to User Centered Design.
Midterm Exam Review IS 485, Professor Matt Thatcher.
Design and Evaluation of Iterative Systems n For most interactive systems, the ‘design it right first’ approach is not useful. n The 3 basic steps in the.
Recap of IS214. Placing this course in context Creating information technology that helps people accomplish their goals, make the experience effective,
Course Wrap-Up IS 485, Professor Matt Thatcher. 2 C.J. Minard ( )
Software Development Overview CPSC 315 – Programming Studio Spring 2009.
Usability 2004 J T Burns1 Usability & Usability Engineering.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 20, 2005.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 22, 2004.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 18, 2007.
Software Development Overview CPSC 315 – Programming Studio Spring 2008.
Mid-Term Exam Review IS 485, Professor Matt Thatcher.
Agile software development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions.
User Experience Design Goes Agile in Lean Transformation – A Case Study (2012 Agile Conference) Minna Isomursu, Andrey Sirotkin (VTT Technical Research.
Web Design Process CMPT 281. Outline How do we know good sites from bad sites? Web design process Class design exercise.
A Day in the Life of a UX Practitioner 21 January 2013 Dr Chandra Harrison.
Usability 2009 J T Burns1 Usability & Usability Engineering.
1. Learning Outcomes At the end of this lecture, you should be able to: –Define the term “Usability Engineering” –Describe the various steps involved.
류 현 정류 현 정 Human Computer Interaction Introducing evaluation.
Product Development & User Testing
Predictive Evaluation
AGILE Methodology. AGILE  derived from the word ‘agile manifesto’, also called the Manifesto for Agile Software Development which is a formal proclamation.
1 Usability of Digital Libraries Sanda Erdelez & Borchuluun Yadamsuren Information Experience Laboratory University of Missouri – Columbia USA Libraries.
Testing Challenges in an Agile Environment Biraj Nakarja Sogeti UK 28 th October 2009.
Interaction Design Process COMPSCI 345 S1 C and SoftEng 350 S1 C Lecture 5 Chapter 3 (Heim)
Human Computer Interaction
Usability testing. Goals & questions focus on how well users perform tasks with the product. – typical users – doing typical tasks. Comparison of products.
Introducing Evaluation: why, what, when, where Text p Text p 317 – 323;
Interaction Design CMU. Today’s objectives Continue Design approaches (UCD, ACD)  User-Centered Design  Activity-Centered Design.
Chapter 12/13: Evaluation/Decide Framework Question 1.
Level 2 Prepared by: RHR First Prepared on: Nov 23, 2006 Last Modified on: Quality checked by: MOH Copyright 2004 Asia Pacific Institute of Information.
New Media Research Methods- Part 1 Planning stage: Using Methods, Data and Tools to explore User’s Experience. How methods relate to research questions?
Innovation insight Peter H. Jones, Ph.D. Dayton, Toronto redesignresearch.com designdialogues.net A Bag of Tricks: What is the Right Mix of Methods?
Usability Testing Chapter 6. Reliability Can you repeat the test?
Chapter 12: Introducing Evaluation. The aims To illustrate how observation, interviews and questionnaires that you encountered in Chapters 7 and 8 are.
Chapter 7 Interactive Design and Prototyping Human Performance Engineering Robert W. Bailey, Ph.D. Third Edition.
Software Engineering User Interface Design Slide 1 User Interface Design.
Chapter 12: Introducing Evaluation. The aims To illustrate how observation, interviews and questionnaires that you encountered in Chapters 7 and 8 are.
User Interfaces 4 BTECH: IT WIKI PAGE:
SOFTWARE ENGINEERING MCS-2 LECTURE # 4. PROTOTYPING PROCESS MODEL  A prototype is an early sample, model or release of a product built to test a concept.
Usability Engineering Dr. Dania Bilal IS 582 Spring 2006.
Design Process … and some design inspiration. Course ReCap To make you notice interfaces, good and bad – You’ll never look at doors the same way again.
Chapter 12/13: Evaluation/Decide Framework. Why Evaluate? Why: to check that users can use the product and that they like it. Designers need to check.
CS5714 Usability Engineering Usability Inspection Copyright © 2003 H. Rex Hartson and Deborah Hix.
Agile 101. Feasibility Study SDLC – What is it? Systems Development Life Cycle: The most commonly used, and generally accepted, project management approach..
Challenges in Agile Unclear project scope, multiple iterations, minimal documentation, early and frequent testing needs and active stakeholder involvement.
Innovation insight Peter H. Jones, Ph.D. Dayton, Toronto redesignresearch.com designdialogues.net.
Project Breakdowns HCDE 492/592 Winter 2014.
Methodologies and Algorithms
User-centred system design process
Design.
Gary Hughes, South Oakleigh College
SysML V2: User-Centered Design Approach
CS 321: Human-Computer Interaction Design
SY DE 542 User Testing March 7, 2005 R. Chow
Process Models Coming up: Prescriptive Models.
Usability Techniques Lecture 13.
Gathering Systems Requirements
Gathering Systems Requirements
Presentation transcript:

Agile Usability Testing Methods Glenn Teneycke

What is Agile? Agile is group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self- organizing cross-functional teams. Agile methods promote a disciplined project management process that requires frequent inspection and adaptation Most Agile development methods involve development iterations, teamwork, collaboration, and process adaptability throughout the life-cycle of the project.

Agile vs. Waterfall

Reality Check Usability testing methodologies tend to be best suited for the traditional waterfall approach Increasing number of projects are a hybrid of Agile and Waterfall. They use some Agile methodologies but not all As a result UX professionals need to embrace some of Agile Usability testing methodologies

Summative Usability Testing Summative usability testing is done later in the process to help measure the usability of a component or identify problems with it The usability requirements should be task-based, and should tie directly to product requirements, including results from analytic tools such as personas, scenarios, and task analysis. Testing may validate a number of objective and subjective characteristics, including task completion, time on task, error rates, and user satisfaction.

Formative Usability Testing Done in the early stages of the project to help guide the design Focus is on whose goal is not primarily to find usability problems that need to be fixed, but to assess the overall user experience and understand users’ reactions to different ideas. This can include comparative testing—that is, soliciting feedback on multiple solutions to a design problem

Formative Testing in Agile Formative testing is used in Agile because Quick turnaround Can fix problems before coded Minimal reporting (team participates in testing) Formative testing is primarily used because it allows the opportunity to influence design direction before significant development is completed

Typical Methods Formative Methods include: Heuristic evaluation Paper Prototyping of concepts Thinking-aloud testing Contextual Inquiry Summative Methods include: Time trials Task completion Focus Groups

Summative Testing in Agile Summative testing is not used as often in Agile because: Creating usability reports is time consuming– even short ones Captures big initial problems, hides smaller ones Collects information that is never used

Agile Usability Testing Best Practices

Recruiting User Pools Set Up User Pools early in the planning process This can be one of the biggest challenges in a project

User Proxies Ideal test subjects are the actual users but getting their time can be challenging These can include actual users, quality assurance, help desk support, work colleagues and subject matter experts Use each group depending on what you want to test Some things need to be tested with the actual users in the real world. However some design decisions don’t depend on that background. Some interactions can be tested on user proxies.

Number of Participants Obstacles to usability testing include the expense and time to test users Based on Jacob Nielsen's assertion that you need to test a minimum of 5 users Testing even 1 user is better then testing none at all. interactions can be tested on user proxies.

Reporting Formative reporting usually take the format of a highlights video or excel list of issues Seldom do long reports RITE method the team sees the issues first hand

Contextual Inquiry Interviews are conducted in the user’s work environment. The researcher observes the users do their own work tasks and discusses any issues they may have. In addition, the user may share past stories they are relevant to the project.

Summary Agile / Waterfall Hybrids require UX teams to adapt their approach Even in a Waterfall project more Formative Usability Testing should be done

Questions?