24
www.flupa.eu 1 Usability and User- Centered Design Agile Tour 2010 Luxembourg Lou Schwartz

Usability and User-Centered Design in agile developments

Embed Size (px)

DESCRIPTION

Who FLUPA are? What is usability? How to ensure the usability of a software? User Centered Design in agile projects

Citation preview

www.flupa.eu

1

Usability and User-Centered Design

Agile Tour 2010Luxembourg

Lou Schwartz

www.flupa.eu

2

• Who we are?• What is usability?• How to ensure the usability of a software?• User Centered Design in agile projects

Plan

www.flupa.eu

3

• Who we are?• What is usability?• How to ensure the usability of a software?• User Centered Design in agile projects

Plan

www.flupa.eu

4

France Luxembourg Usability Professionals’ Association

• Local chapter of UPA http://www.upassoc.org– 46 local chapters– 3055 members in 57 countries

• Objectives of FLUPA– Promoting usability of HCI– Increase public awareness of user centered design and

ergonomics approach – Lead a network of professionals

• Members with various profiles– Psychologists, ergonomists, designers, software

engineers and developers, communication specialists …– Professionals, administration, researchers, students, …

www.flupa.eu

5

France Luxembourg Usability Professionals’ Association

• 3 units– Luxembourg, Grenoble, Paris

www.flupa.eu

6

France Luxembourg Usability Professionals’ Association

• 3 units– Luxembourg, Grenoble, Paris

• Organization of events– Breakfast around a theme, World Usability

Day, barbecues, …

Next events

• 11/11 Lux – World Usability day: usability and communication

• 17/11 Grenoble – Breakfast: usability and video games

• xx/12 Lux – Breakfast: mock-up design

• xx/01 Paris – Breakfast: tactile interfaces

www.flupa.eu

7

France Luxembourg Usability Professionals’ Association

• 3 units– Luxembourg, Grenoble, Paris

• Organization of events– Breakfast around a theme, World Usability

Day, barbecues, …

• Communication– Web site www.flupa.eu – Forum http://forum.flupa.eu/phpbb/ – Twitter http://twitter.com/assoFlupa – Newsletter– …

www.flupa.eu

8

• Who we are?• What is usability?• How to ensure the usability of a software?• User Centered Design in agile projects

Plan

www.flupa.eu

9

What is Ergonomics?Science of designing user interactions

Ergonomics

Usefulness Usability

www.flupa.eu

10

Why ergonomics?• Ensures the usability

– Following the logic of users

– Fulfilling performance, efficiency criteria

– Understanding the user's capabilities and limits http://www.cadfanatic.com/2009/08/solidworks-usability-testing/

www.flupa.eu

11

Why ergonomics?• Ensures the usability

– Following the logic of users

– Fulfilling performance, efficiency criteria

– Understanding the user's capabilities and limits

• To avoid accidents/incidents

http://www.cadfanatic.com/2009/08/solidworks-usability-testing/

www.flupa.eu

What is usability?• Official definition (ISO 9241-11:1998)

– “The extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use”

– Effectiveness

– Efficiency

– Satisfaction

12

www.flupa.eu

13

• Who we are?• What is usability?• How to ensure the usability of a software?• User Centered Design in agile projects

Plan

14

www.flupa.eu

How to ensure the usability of a software?• User centered design process (ISO 13407)

• Design process that places the user in the middle of the project

• Concentrates the efforts to answer to the user needs/objectives

• Principles• Active participation of users • Comprehension of users needs and users tasks• Develop only what is useful to be supported by the tool• Development by iterations• Multidisciplinary

15

www.flupa.eu

How to ensure the usability of a software?• Conducted by a

usability expert

• Who uses methods (ISO 16982 and others)• Observation of users • Evaluation by an expert• Questionnaires• Interviews• Card sorting• Personas• Focus groups• …

Do we need a UCD approach?

Understand and specify context of use

Specify needs of users and objectives of organization

Propose design or develop software

Evaluation of design / requirements

The system covers the users and organization requirements

www.flupa.eu

16

• Who we are?• What is usability?• How to ensure the usability of a software?• User Centered Design in agile projects

Plan

www.flupa.eu

UCD vs Agility ?Compatibilities17UCD principles – ISO 13407 Agility

Iteration of design solutions Iterative cycle

An appropriate allocation of functions between users and technology

The active involvement of users and a clear understanding of user and task requirements

Multi-disciplinary design

Agile values UCD

Customer collaboration over contract negotiation

17

UCD principles – ISO 13407 Agility

Iteration of design solutions Iterative cycle

An appropriate allocation of functions between users and technology

Limits of what has to be develop are defined by the product ownerSimplicity--the art of maximizing the amount of work not done--is essential.

The active involvement of users and a clear understanding of user and task requirements

Multi-disciplinary design

Agile values UCD

Customer collaboration over contract negotiation

UCD principles – ISO 13407 Agility

Iteration of design solutions Iterative cycle

An appropriate allocation of functions between users and technology

Limits of what has to be develop are defined by the product ownerSimplicity--the art of maximizing the amount of work not done--is essential.

The active involvement of users and a clear understanding of user and task requirements

One user is implied throughout the project (the product owner)• Defines requirements• Remembers the context of use• Validates the work doneBut can imply some users as “chicken”

Multi-disciplinary design

Agile values UCD

Customer collaboration over contract negotiation

UCD principles – ISO 13407 Agility

Iteration of design solutions Iterative cycle

An appropriate allocation of functions between users and technology

Limits of what has to be develop are defined by the product ownerSimplicity--the art of maximizing the amount of work not done--is essential.

The active involvement of users and a clear understanding of user and task requirements

One user is implied throughout the project (the product owner)• Defines requirements• Remembers the context of use• Validates the work doneBut can imply some users as “chicken”

Multi-disciplinary design Few multi-disciplinary only developers and product owner (business view) at minimumBut multi-disciplinary is not rejected

Agile values UCD

Customer collaboration over contract negotiation

UCD principles – ISO 13407 Agility

Iteration of design solutions Iterative cycle

An appropriate allocation of functions between users and technology

Limits of what has to be develop are defined by the product ownerSimplicity--the art of maximizing the amount of work not done--is essential.

The active involvement of users and a clear understanding of user and task requirements

One user is implied throughout the project (the product owner)• Defines requirements• Remembers the context of use• Validates the work doneBut can imply some users as “chicken”

Multi-disciplinary design Few multi-disciplinary only developers and product owner (business view) at minimumBut multi-disciplinary is not rejected

Agile values UCD

Customer collaboration over contract negotiation Ok

www.flupa.eu

UCD vs Agility ?Impediments

18

Agile values UCD

Individuals and interactions over processes and tools

Adapt methods to the agile contextsimplify to do them in only one iterationlimit the production of documentation, …

Working software over comprehensive documentation

Reacting to change over following a plan

Agile values UCD

Individuals and interactions over processes and tools

Adapt methods to the agile contextsimplify to do them in only one iterationlimit the production of documentation, …

Working software over comprehensive documentation

Do only what is necessaryLighten the results to enhance their impact and usefulnessDon’t need to use great software to do this

Reacting to change over following a plan

Agile values UCD

Individuals and interactions over processes and tools

Adapt methods to the agile contextsimplify to do them in only one iterationlimit the production of documentation, …

Working software over comprehensive documentation

Do only what is necessaryLighten the results to enhance their impact and usefulnessDon’t need to use great software to do this

Reacting to change over following a plan Light global vision can be defined during the sprint 0Maybe do an epic during the project on usability to ensure the homogeneityFocus on the iteration requirements, don’t try to do all at the same time

www.flupa.eu

How to do agile UCD ?

The proposal of adaption the most frequently cited are• Imply one or more usability expert(s) in your team

• Imply all actors in the team meetings

– Stand up meetings, specifications, demonstrations, …

– Sometimes it is proposed to add interfaces design meetings

19

www.flupa.eu

How to do agile UCD ?• Keep iterative cycle• Work in parallel but in the same team

– With one sprint of timing delay– Or in the same sprint, cutting the sprint into 3 phases

• Redefine artefacts of work

20

www.flupa.eu

How to do agile UCD ?• Keep iterative cycle• Work in parallel but in the same team

– With one sprint of timing delay– Or in the same sprint, cutting the sprint into 3 phases

• Redefine artefacts of work

21

www.flupa.eu

How to do agile UCD ?• Adapt usability methods to the agile context

– Simplify– Use only methods usable in agile– Change the granularity of usability investigations– Change the reporting of usability investigations– Possibility to dedicate an epic to the review of the homogeneity– Use the cycle 0 for usability investigations

22

23

www.flupa.eu

Some good references• UCD

– Don’t Make Me Think by Steve Krug (ISBN-10: 0789723107)– UPA http://www.upassoc.org/usability_resources/

• Agile and UCD– Jean-Claude Grosjean’s Weblog

• http://www.qualitystreet.fr/ • Coaching Agile, Experience Utilisateur, Tests Logiciels et Ergonomie IHM

– Miller, Lynn. Case Study of Customer Input For a Successful Product, Proceedings of the Agile 2005 conference.

• http://agileproductdesign.com/useful_papers/miller_customer_input_in_agile_projects.pdf

– Sy, Desiree. Adapting Usability Investigations for Agile User-Centered Design., Journal of Usability Studies, Volume 2, Issue 3, May 2007, pp. 112-132 http://www.upassoc.org/upa_publications/jus/2007may/agile-ucd.html

– Schwartz, L. and al., Comment concilier agilité et conception centrée utilisateurs dans un projet de développement?, IHM’09, http://portal.acm.org/citation.cfm?id=1629881#

– Guide d’intégration de CCU à SCRUM (in French, not yet validated) • http://pyxis-tech.com/fr/expertise/guide-dintegration-de-ccu-a-scrum

www.flupa.eu

24

Thanks for your attention !

[email protected] events• 11 Nov, Lux – World Usability day: usability and

communication

• 17 Nov, Grenoble – Breakfast: usability and video games

• December, Lux – Breakfast: mock-up design

• January, Paris – Breakfast: tactile interfaces

Contacts

Web site www.flupa.eu

Forum http://forum.flupa.eu/

Twitter @assoFlupa