STORY MAPPING Recover from Flat Backlogs with User Story Mapping Tracy Whitehill Agile Team Coach
STORY MAPPING Recover from Flat Backlogs with User Story Mapping Tracy Whitehill Agile Team Coach.
Dec 26, 2015
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
STORY MAPPING
Recover from Flat Backlogs with User Story Mapping
Tracy WhitehillAgile Team Coach
How good are we at predicting what customers need?
2
How good are we at predicting what customers need?
45%
19%16%
13%
7%NeverRarelySometimesOftenAlways
From: A Standish Group 2002 study
Feature/function usage in the software industry
always
often
sometimes
rarely
never
We want to Shift the Process from a Requirements Delivery Process…
False Assumptions:1. The customer knows what he wants2. The developers know how to build it3. Nothing will change along the way
4
…To a Requirements Discovery Process
Reality:1. The customer discovers what he
wants2. The developers discover how to
build it3. Many things change along the
way
Challenges with One dimensional backlogs
• Do you understand the workflow?
• Are you able to see the relationship of larger stories to child stories?
• How do you validate that your backlog is complete?
• What context do you use for prioritization?
User tasks are decomposed into smaller
tasks and organized into activities
User Story Maps help us plan releases in complete and
valuable slices
Activity(Theme/
epic)
Activity(Theme/
epic)
Activity(Theme/
epic)
Activity(Theme/
epic)
Activity(Theme/
epic)
Action(story
)
Action(story
)
Action(story
)
Action(story
)
Action(story
)
Action(story
)
Action(story
)
Action(story
)Action(story
)
Action(story
)
Action(story
)
Action(story
)
Action(story
)
Workflow sequence
Prio
rity
First Release
Action(story
)
NextRelease
Anatomy of a User Story MapH
igh
Low
backbone
walking skeleton
Action(story
)
10
Minimal Viable Product - MVPMVP is “the version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.”
– Eric Ries, The Lean Startup
11
BuildLearn
Minimize time thru the loop
Eric Ries: The Lean Startup
1) What do we need to
learn?
2) How can we measure it?
3) What is the simplest thing to build to measure
it?(MVP)
Validated Learning: the Build-Measure-Learn cycle
Measure
12
1. Problemtop 3 problems
Existing alternatives
4. Solutiontop 3 features
8. Key metricse.g. AARRR
3. Unique value
propositionClear compelling
message. Why makes you different?
2. Customer segments
Target customers
Early adopters?
9. Unfair advantage
Not easily copied or bought
5. ChannelsPath to
customers
7. Cost StructureCustomer acquisition, distribution, people, etc.
6. Revenue streamsRevenue model, life time value, revenue, gross
margin
Lean Canvas: Ash Maurya
Product Market
Lean Canvas
Lean Canvas, from Ash Maurya: Running Lean. Licensed under Creative Commons-Attribution-Share Alike 3.0*AARRR metrics: acquisition, activation, revenue, retention, referral (Dave McClure)
13 1. Problem• Inefficient energy
usage• Age & disability
create difficulty• ?
Existing alternatives
• Hire help• Perform manually• ?
4. Solution• Voice command
lights, appliances• Scheduled tasks• Motion
detection• ?
8. Key metrics• # requests 4 info• # subscriptions• ?
3. Unique value proposition
• Integrated control of ALL home systems
• Free installation• ?
2. Customer segments
• Elderly/disabled• Eco-conscious• ?
Early adopters?
9. Unfair advantage
• Patents• ?
5. Channels• Infomercials• Social media• ?
7. Cost Structure Marketing, product design, ?
6. Revenue streams Hardware sales, subscription, ?
Lean Canvas, from Ash Maurya: Running Lean. Licensed under Creative Commons-Attribution-Share Alike 3.0Product Market
Partial Lean Canvas: Home Automation
Action (story
)
Action (story
)
Action (story
)
Action (story
)
Action (story
)
Action (story
)
Action (story
)
Action(story
)Action (story
)
Action (story
)
Action (story
)
Action (story
)
Action (story
)
Action(story
)
Workflow sequence
Action (story
)
Story Map Activity Part 11. Choose a Customer Segment from your Lean
Canvas
2. One person plays the Customer role
3. Ask what the customer wants, capture each idea on a post-it
1. Arrange in order of workflow
2. Group items into common activities or categories
3. Arrange top to bottom by priority
Activity(Theme/
epic)
Activity(Theme/
epic)
Activity(Theme/
epic)
Activity(Theme/
epic)
Activity(Theme/
epic)
Action (story
)
Action (story
)
Action (story
)
Action (story
)
Action (story
)
Action (story
)
Action (story
)
Action (story
)Action (story
)
Action (story
)Action (story
)
Action (story
)
Action (story
)
Workflow sequence
Prio
rity
Action (story
)
Story Map Activity Part 2H
igh
Low
16
Story Map Activity Part 3
1. Draw the line for your MVP
2. Draw the line for subsequent Releases
Activity(Theme/
epic)
Activity(Theme/
epic)
Activity(Theme/
epic)
Activity(Theme/
epic)
Activity(Theme/
epic)
Action(story
)
Action(story
)
Action(story
)
Action(story
)
Action(story
)
Action(story
)
Action(story
)
Action(story
)Action(story
)
Action(story
)
Action(story
)
Action(story
)
Workflow sequence
Prio
rity
Action(story
)
Hig
hLo
w
Action(story
)
MVP
NextRelease
Reading the activities across the top of the system helps us understand end-to-end
use of the system.
User Story Mapping is Collaborative & Fosters Co-
Ownership
User Story Maps help us see things from a user’s
perspective
Colors for different user
personas
With User Story Mapping you can test for Gaps by Walking
the Map
Activity(Theme/
epic)
Activity(Theme/
epic)
Activity(Theme/
epic)
Activity(Theme/
epic)
Activity(Theme/
epic)
Action(story
)
Action(story
)
Action(story
)
Action(story
)
Action(story
)
Action(story
)
Action(story
)
Action(story
)Action(story
)
Action(story
)
Action(story
)
Action(story
)
Action(story
)
Workflow sequence
Prio
rity
MVP
Action(story
)
NextRelease
Anatomy of a User Story MapH
igh
Low
Action(story
)
Related Documents
