personas, scenarios, user stories

Post on 17-May-2015

9.455 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

DESCRIPTION

A brief for today's le

TRANSCRIPT

Personas, scenarios, user storiesValeria Gasik, Zahhar Kirillov, Daria Tokranova

Topics

• Personas

• Scenarios

• User stories

PersonasOne of the user-centered design approaches

• Based on interviews, observation, research

• Primary, secondary (+ supplementary)

• Serve as a guide to the design process

• Does not substitute involving real users in the process

>

John Smith Robert

Personas

Irene, 28

Background: real estate agent, dance instructor

Description: Irene has a hectic life. Dance competitions are approaching and as an instructor, she needs to schedule extra trainings for 15 people, which should also fit into her own busy calendar. Irene is mostly connected through mobile.

Goals:

• Irene needs a easy way to schedule training events for 15 people

• She wants to quickly see which days are suitable for others on the go, since she mostly uses internet on her mobile

Example

Example

Scenarios

Scenarios describe likely goal-driven interactions between types of users

(personas) and the system.

It’s morning and Irene stops at a gas station on her way to a meeting. While filling the tank she decides to quickly check whether her dance group has agreed upon the next training day.

Example

Irene takes her phone. She logs in to a service and sees and overview of proposed dates. Irene notices that only 11 people of 15 has replied. She also sees that for most next Monday and Saturday suited best. Irene needs the final answer soon, so she send a reminder to those who have not yet replied. Then she closes the phone and continues her journey.

Scenarios

• Consists of goals, expectations, motivations, actions and reactions

• Aims to mirror the real context and usage

• Does not yet include system-specific solutionsE.g.: “Robert clicks on a green button...” Better : “Robert proceeds to...”

User StoriesWritten sequences of actions and events that lead to an outcome

• Good stories are standalone, short and testable

• Bridge between users, designers and developers

• A quick way to process new requirements

User Stories

“As a <role>, I want to <do what > so that I could <benefit how>.”

User Stories

“As an organizer, I want to easily schedule an event for several people so that I could teach a dance class.”

Example

User Stories

“As an organizer, I want to sent a reminder to those who have not yet replied so I will know which day suites best for all.”

Example

User Story

• Describes one specific need

• Not too detailed

• Testable

“As an organizer I want to click on various days in calendar

I want to provide several meeting day options.”

“As an organizer, I want to easily schedule an event for several people so that I could teach a dance class.”

“As an organizer, I want to provide few options for upcoming meeting day”

“As an organizer, I want to invite people to choose the best day for them”

“As an organizer, I want check what days others have proposed.”

top related