SCENARIO BASED PLANNING FOR ENGINEERS

Monica GranfieldUX Design + Strategy

@monicagr

January 29, 2017

How do you want your users to feel, when they use what

you have created?

3

...like this?

4

...or like this?

Scenario Based Planning

6

A method of creating and planning that assures you will meet the customer and business goals, for your product , in a light, flexible + rapid fashion.

Scenario based engineering is...

What does that mean?

8

It means the difference

between delivering an

experience or a list of

features.

Why use it?

10

● Focus, on small features, derived from a user centered scenario, for

fast + efficient development.

● When grouped together to build out a scenario, small features don’t

just deliver a list of features, but instead, deliver a more

meaningful experience to the user.

● Alleviate pain points, allowing users to complete tasks,

more efficiently + effectively.

Why use scenario based engineering...Deliver not just code, deliver value to your users

How does it work?

12

I want to have Macaroni + Cheese for dinner.

13

Boxed

Frozen

Fresh

Store made

Homemade

Take-out…..

14

Milk

Bread

Orange Juice

Pasta

Grocery list - “What am I out of ?”

15

Mac + Cheese?

16

Vs.

17

Milk

Bread

Pasta

Cheese

Butter

Breadcrumbs

Grocery list - “What do I need to make mac + cheese ?”

18

Mac + Cheese...

+ + +

19

Mac + Cheese !

20

● Plan what you work on, based on user centric scenarios.

● Scope small experiences into deliverables that can be built on to

extend the scenario over time.

● Accomplish, a desirable experience.

How does scenario based engineering work?

21

Plan…

Scenario

PPE1

Release Goal PPE2

goal

PPE3

goal

goal

task

task

task

(Pain Points + Enhancements)

S

S

S

(Stories)

22

ProductCreating products for developers, like John, to be more productive and efficient at his job.

Develop scenarios

Understand which user(s) you are creating for, and what tasks the user will perform to generate a desired outcome. Tell the story of what the user wants to accomplish.Scenarios allow you to hypothesize possible outcomes for various situations, so you can design to them.

Plan…

John, a Jr. Developer

Understand the user you are creating the experience for.

23

Develop Scenarios - Example

John, a junior developer, uses an IDE to write his code. He prefers to keep his environment

set, so that the environment remains the same each time he uses the IDE. John likes to work

in coffee shops or small office enclaves and this means he uses his laptop, with a smaller

screen, while working. He finds using the laptop monitor challenging, as he ends up scrolling

the screen for much of the time while working and this slows him down. John also uses a

component library to create the user interface. The library currently resides on a website and

John thinks it would be a great idea if he could somehow access the library from within the

IDE, to move through coding in a faster more efficient way.

Plan…Create the user centric scenario, tell the story.

S

RG

PE

G

TT T

SS S

24

Establish a Release Goal

To increase productivity, by addressing the context of the devices used

for the development environment, and access to other useful assets.

Plan…Accomplish, based on user centric scenarios.

S

RG

PE

G

TT T

SS S

25

Identify any Pain Points + Enhancements

● Keeping the environment setup the same “sticky” for product reuse.

● Scrolling around on a smaller screen is tiring and slows down

productivity.

● No integrated access to a UI component library.

Plan…Ask how you can improve the experience

S

RG

PE

G

TT T

SS S

26

Establish Goals to solve the pain points and feature enhancements

● Persist the setting and configurations of the IDE workspace, so that wherever a user

accesses it from, it retains settings and context and the user can pick up working where

they left off.

● Alleviate the need to need to scroll as much, when on a laptop or lower resolution

device.

● Incorporate a way for the user to specify and access a component library of choice,

when using the IDE.

Plan…What you work on based on user centric scenarios.

S

RG

PE

G

TT T

SS S

27

Break each goal down into user tasks

Persist the setting and configurations of the IDE workspace, so that wherever a user

accesses it from, it retains settings and context and the user can pick up working where s/he

left off.

● User opens the IDE and configures the environment, to include tools and locations s/he

like to work with.

● User manipulates the IDE workspace configuration as s/he works.

● User logs out and logs in from another device, finding the IDE workspace in the same

state, as last use.

Plan…Scope the goals into user tasks for rapid development.

S

RG

PE

G

TT T

SS S

28

Break each task down into stories

User opens the IDE and configures the environment, to include tools and locations s/he like

to work with.

● User locates specific settings around a configuration

● User manipulates and configures layout and arrangement of the workspace

environment

Plan…Scope the goals into tasks for rapid development.

S

RG

PE

G

TT T

SS S

29

Deliver...Results based on user centric scenarios.

Goal Tasks

Stories

30

Deliver...Break the Tasks down into stories or issues.

small, focused stories for rapid iteration and deployment, that can be usefully, and rapidly built out.

=

31

VS.A list of disparate features.

32

AccomplishedAn experience where users complete tasks, more efficiently + effectively.

Recap

34

● User centric scenarios are used for mapping out, scoping and

planning the experience you want to deliver.

● Delivers focused, desirable, scaleable experiences, in a lean

and rapid fashion.

● Alleviates pain points, allowing users to complete tasks, more

efficiently + effectively, while delivering an enhanced experience.

Scenario Based Engineering

THANK YOU

plus.google.com/+RedHat

linkedin.com/company/red-hat

youtube.com/user/RedHatVideos

facebook.com/redhatinc

twitter.com/RedHatNews

@monicagr