Lean Product Design Tools

Product Thinking
( things we build are products )

Introduce yourself as your product

Why (purpose) vs How (tools)

1) Why are you building? ( chartering )
2) Who is buying (in)?

( personas )

3) What do they need?

( story mapping )

4) Where do we start?

( slicing )

5) When is there value?

( story testing )

Pragmatic Personas
( who is getting value? )

Personas are design targets

Personas represent people & clarify product value

Todays Product: A New POS

( simple charter )
Create a Point of Sale application
10 local stores
Application runs only on registers
Technology choices are made ( e.g. Java )
Another system provides item price & description

Who are the POS Personas?

Emergent Personas

Lasting Personas

Create Your Products Personas

First create a list of personas then fill out one or two
Choose a name
( sticky name alliteration helps )
------------------------------------------------------------------------------------Add an image

( a conversation starter )

------------------------------------------------------------------------------------Add a description
Value from product

( who is this person? )

- time at job
- knowledge of domain
- FT / PT
- level of engagement

( what is our sell? )

- financial benefit?
- increased productivity?
- fewer steps?
- easier to use?

Persona Questions?

Story Mapping
( what are the users needs? )

Story Maps Tell the Big Picture

Avoid Templates
As _______ I need to _________ so that I can _________

user

story

value

As ____ I need to ____ so that ____

As ____ I need to ____ so that ____

As ____ I need to ____ so that ____

As ____ I need to ____ so that ____

As ____ I need to ____ so that ____

As ____ I need to ____ so that ____

As ____ I need to ____ so that ____

As ____ I need to ____ so that ____

As ____ I need to ____ so that ____

As ____ I need to ____ so that ____

As ____ I need to ____ so that ____

As ____ I need to ____ so that ____

Promote Discussion and Context

As _______ I need to _________ so that I can _________

persona

story

test

A Simple Story Map

Persona

Story Title

Story Title

Story Title

Image

- Story Test

- Story Test

- Story Test

- Story Test

- Story Test

- Story Test

- Story Test

- Story Test

- Story Test

- Story Test

- Story Test

- Story Test

Desc

Value

Story maps contain user stories

The What
User task or system event

Story

The Completion Measures

User satisfaction / business value

Tests

The How
Design and coding work

Tasks

The Estimates
Effort to complete tasks

Cost

Example User Story

(Less that 5 words in title, details live in tests)
Story Name: Add Item To Sale
Story Tests:
Show that 1 or more items can be added to a
sale with no items.
Show that more than 1 items can be added
to a sale with existing items
Ensure that adding an invalid sku returns an
error, and does not add the item to the sale.
< there is a never ending list of story tests >

Traditional Story Writing Session

Persona Driven Authoring

Once she
finds the
loan

Story Mapping Session

Lets Jam!
( fearless story jams )

Steps for Story Mapping

Name the high level goals for a persona
( what are her goals? )
scenarios or activities
Walk a day in the life for each activity
( what does she need? )
user tasks system tasks
Back up and re-tell the experience
( what are the variations? )

Two Simple Guides

Mile wide, inch deep

More writing, less talking

Lets Map the Point of Sale

The Animated Version

Open
Registr

Make
Sales

Cross /
Up Sell

Log In

Track
Sales

Scan
Add
Item

Calc
Tax

Count
Cash

Track
Errors

Key In
Item

Log Out

Calc
Total

Take
Paymnt
Cash

Print
Receipt

Add
Survey

Calc
Taxable

Take
Gft Crd

Gift
Recpt

Ask
Reward

Set Not
Taxable

Take
Credit

Email
Recpt

Take
Coupon
Take
StrCrdt

Spin thru - Back up and find variations & dead ends

Maps Foster Co-Ownership

Maps Improve Planning

Sketches Augment Maps

What are your story maps?

Activity

Activity

Task

Task

Task

Task

Task

Task

Task

Activity
Task

Task

Task

Task

Task

Task

Task

Task

Task

Task
Task
Task

1) Activities (goals) - 2) User Tasks - 3) Variations

10

Story Mapping Questions?

Slicing

Slicing a User Experience

Open
Registr

Make
Sales

Cross /
Up Sell

Log In

Track
Sales

Add
Item

Calc
Tax

Count
Cash

Track
Errors

Scan
Item
Key In
Item

Log Out

Calc
Total

Take
Paymnt

Print
Receipt

Add
Survey

Calc
Taxable

Take
Cash

Gift
Recpt

Ask
Reward

Set Not
Taxable

Take
Credit

No
Recpt

11

Slicing a Release
Open
Registr

Make
Sales

Cross /
Up Sell

Log In

Track
Sales

Add
Item

Calc
Tax

Count
Cash

Track
Errors

Scan
Item
Key In
Item

Log Out

Calc
Total

Take
Paymnt

Print
Receipt

Add
Survey

Calc
Taxable

Take
Cash

Gift
Recpt

Ask
Reward

Set Not
Taxable

Take
Credit

No
Recpt

Testing

Collaboration / Validation

Story Tests Define Done

12

Acceptance (Story) Tests

Start creating or thinking about story tests early
(Story tests help size or clarify stories)
(Keep adding tests authoring, planning , )

Engage testers to create or automate story

tests (Upstream from planning when possible)
Keep story tests clear, testable, valuable
Automate story tests (as early as possible)

Tests In Disguise

For example

If , then

Add Acceptance Tests:

Add Item to Sale with Keyboard
Calculate Sales Tax
Show Total for Sale
Process Payment
Print Receipt

13

Validating Value
Developer runs acceptance tests
Business runs acceptance tests with
developer, testers augment the process
Story points are burned for the release

Questions?
_________________________________________

Coaching and Developing Agility

_________________________________________
david.hussman@devjam.com
www.devjam.com
2013 DevJam - All rights reserved.

14