lean product design tools
DESCRIPTION
tadaTRANSCRIPT
1
Lean Product Design Tools
Product Thinking ( things we build are products )
Introduce yourself as your product
2
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 )
Why (purpose) vs How (tools)
Pragmatic Personas ( who is getting value? )
Personas are “design targets”
Personas represent people & clarify product value
3
Today’s 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
4
Lasting Personas
Create Your Product’s 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? ) ( what is our sell? )
- time at job - financial benefit?
- knowledge of domain - increased productivity?
- FT / PT - fewer steps?
- level of engagement - easier to use?
Persona Questions?
5
Story Mapping
( what are the user’s needs? )
Story Maps Tell the Big Picture
“As _______ I need to _________ so that I can _________”
user story value
Avoid Templates
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 ____
6
“As _______ I need to _________ so that I can _________”
persona story test
Promote Discussion and Context
A Simple Story Map
Persona
Image
Desc Value
Story Title
- Story Test
- Story Test
- Story Test
- Story Test
Story Title
- Story Test
- Story Test
- Story Test
- Story Test
Story Title
- Story Test
- Story Test
- Story Test
- Story Test
Story maps contain user stories
The What Story
– User task or system event
The Completion Measures Tests
– User satisfaction / business value
The How Tasks
– Design and coding work
The Estimates Cost
– Effort to complete tasks
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 >
7
Traditional Story Writing Session
Persona Driven Authoring
“Once she
finds the
loan …”
Story Mapping Session
8
Let’s 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?” )
More writing, less talking
Mile wide, inch deep
Two Simple Guides
9
Let’s Map the Point of Sale
The Animated Version
Spin thru - Back up and find variations & dead ends
Open
Registr
Log In Track
Sales
Add
Item
Set Not
Taxable
Scan
Item
Key In
Item
Count
Cash
Take
Gft Crd
Take
Cash
Take
Credit
Take
Coupon
Ask
Reward
Make
Sales
Cross /
Up Sell
Calc
Tax
Calc
Total
Calc
Taxable
Receipt
Add
Survey
Gift
Recpt
Take
Paymnt
Take
StrCrdt
Track
Errors
Log Out Email
Recpt
Maps Foster Co-Ownership
10
Maps Improve Planning
Sketches Augment Maps
What are your story maps?
1) Activities (goals) - 2) User Tasks - 3) Variations
Activity
Task Task Task Task
Task
Task Task
Task
Task
Task
Task
Task
Task
Task
Task
Activity Activity
Task Task
Task
Task
11
Story Mapping Questions?
Slicing
Slicing a User Experience Open
Registr
Log In Track
Sales
Set Not
Taxable
Scan
Item
Key In
Item
Count
Cash
Take
Cash
Take
Paymnt
Take
Credit
Ask
Reward
Make
Sales
Cross /
Up Sell
Calc
Tax
Calc
Total
Calc
Taxable
Receipt
Add
Survey
Gift
Recpt
Track
Errors
Log Out
Add
Item
No
Recpt
12
Slicing a Release Open
Registr
Log In Track
Sales
Set Not
Taxable
Scan
Item
Key In
Item
Count
Cash
Take
Cash
Take
Paymnt
Take
Credit
Ask
Reward
Make
Sales
Cross /
Up Sell
Calc
Tax
Calc
Total
Calc
Taxable
Receipt
Add
Survey
Gift
Recpt
Track
Errors
Log Out
Add
Item
No
Recpt
Testing
Collaboration / Validation
Story Tests Define Done
13
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
14
Validating Value
• Developer runs acceptance tests
• Business runs acceptance tests with
developer, testers augment the process
• Story points are burned for the release
www.devjam.com
Questions?
Coaching and Developing Agility
_________________________________________
_________________________________________
© 2013 DevJam - All rights reserved.