IxDPersonas, Scenarios, User Stories

TLU-HCI Summer School 2013Valeria Gasik, Zahhar Kirillov, Daria Tokranova

What is IxD?

IxD – near-term

Product developmentE-commerceChange ManagementUsability, UXInformation Architecture (IA)

e.g. interface design

IxD – medium-term

Ubiquitous computingNatural InterfacesSustainability

“Human-computer interaction is a discipline concerned with the

design, evaluation and implementation of interactive computing systems for

human use and with the study of major phenomena surrounding them.”

- Hewett, T. et al. 1992, “Lime Green Report”.

State of the art

Context

Where?

Who?

What?

X +2% Y -80% 11:43:33 -10C*

Useful

Technology

Ethical

UsableAppealing

EngagingAccessible

User-centered Design

Personas Scenarios User StoriesUse Cases

PrototypeMVPTesting

Personas

Persona

An imaginative description of a user archetype, which is based on the real research and observations.

Do not substitute testing with and talking to the real people!

Example

http://whereisthebus.blogspot.com/

Example

Name, age

Background

Brief description, “story”

Goals do not mention any practical design solution, eg. “selects a day”

instead of “clicks on a calendar icon”

Scenarios

Scenario

Describes interaction of how the product or system would be used by personas in the real life.

Includes goals, motivations, actions and reactions.

http://resources0.news.com.au/images/2010/06/03/1225874/919424-ipad-menu.jpg

Example

It’s Saturday morning and John is on his way to an airport from the city center. He needs some cash for the taxi.

He goes to a nearest ATM and identifies himself. John specifies that he wants 100 € from his daily account. He hopes to receive small notes so he could pay the taxi driver without big change.

John does not want a receipt. He wants to be sure that he don’t forget his card or money in the ATM.

It’s Saturday morning and John is on his way to an airport from the city center. He needs some cash for the taxi.

He goes to a nearest ATM and identifies himself. John specifies that he wants 100 € from his daily account. He hopes to receive small notes so he could pay the taxi driver without big change.

John does not want a receipt. He wants to be sure that he don’t forget his card or money in the ATM.

ExampleStory background, settings

Motivation (“paying the driver”)

Goal“taking

out some cash”

Actions (e.g. identification, specifying account, not taking a receipt....)

User StoriesUse Cases

User Stories

A simple description template for the (one) goal the user wants to do with your product.

As a (role) I want to do (what),

so I can benefit (how).

As a touristI want to find the cheapest

public transport route from Airport to my Hotel

so I can save money.

User Stories

Epic / Saga user stories

Theme user stories Theme user storiesTheme user storiesTheme user stories

Theme user storiesTheme user stories

Adopted from Mike Cohn

User stories with clear conditions of satisfactions

Use Cases

A step-by-step description of one process, which helps the user (and other actors) to achieve a result.

Components: Use Case, Actors, Steps

Example

Use Case – Search of the cheapest public transport route. Actor – TouristSteps –

1. In search form, specify “from” and “to” locations2. In search form, select day and time of a) arrival or b) departure3. Arrange search results in ascending order with “Price” filter

Use Cases

Use CaseExample

Use Case – Read reviews of the best local shops Actor – TouristSteps – 1, 2, 3..Additional questions > requirements

Who posts reviews? ...How and when reviews are required? ...Who can edit reviews? ...Can a review be rated? How? ...

Today’s To Do

In your blog

1. Describe 1-2 personas

2. Write 1-2 scenarios and few related user stories + use cases, if you want to go into more details

3. Link your posts to workshop’s blogpost of the day

Thursday 25.7

Time to get busy!

We will continue with low fidelity prototypes (paper & online tools).