The document discusses user story mapping as a way to organize a product backlog. It describes ingredients for user story mapping, including user personas, activities, and stories. It shows how user stories can be organized on a board by activity, persona, and release. The document then provides an example case of user story mapping for a company called the Big Idea Group. It outlines their idea for a simple lists mobile app to demonstrate their design and development abilities to customers.

1. User story mapping
for a sane backlog
Margareta Gajne Löfvenholm,
Freelancing UX & Servicedesigner
1 @gajlof, gaine.se

2. Margareta Gajne Löfvenholm,
Freelancing UX & Servicedesigner
@gajlof, gaine.se

3. 3 @gajlof, gaine.se

4. 4 @gajlof, gaine.se

5. 5 @gajlof, gaine.se

6. insane backlogs
100 rows in an excel sheet with 20 columns?
pic from www.amazon.com
6 @gajlof, gaine.se

7. user focus?
it’s in there somewhere
pic from www.amazon.com
7 @gajlof, gaine.se

8. User story mapping
by Jeff Patton
pic from jpattonassociates.com
8 @gajlof, gaine.se

9. pic from www.thoughtworks.com
9 @gajlof, gaine.se

10. ingredients
• service or product
idea
• user personas
• user’s activities
• user stories
pic from visualpun.ch
10 @gajlof, gaine.se

11. 11
user
activity
user
activity
user
activity
user
activity
sub-
activity
sub-
activity
user persona
user story
user story
user story user story
user story
user story
user story
user story
release 1
release 2
release 3
service or
product
idea
@gajlof, gaine.se

12. fika
12 @gajlof, gaine.se

13. our case…
13 @gajlof, gaine.se

14. Idea Brief
Big Idea Group
Our company, the Big Idea Group, BIG for short, is actually a small company that
does outsourced product design and development.
What we’re good at
We’re especially good and building mobile apps – apps for iOS, Android, and
now Microsoft’s mobile platform
Unlike our competitors, we’re good at whole product design. We don't just take
requirements and build what people ask, although we can. Instead we focus on
understanding and solving problems. We use effective discovery practice to
identify minimal viable products. We emphasize maximizing product outcomes
while minimizing the amount we spend on development. In this way we provide a
better return on investment for our customers.
14 @gajlof, gaine.se

15. Idea Brief
Our customers:
Our customers are usually larger organizations who don’t develop software products as their
primary business, but do serve consumers. This includes:
• Banks
• Insurance companies
• Airlines
• Hotel chains
Our challenges
Our customers don’t always understand our key differentiators, especially our ability to
collaborate with them to design successful products. As a consequence we:
• Spend lots of time responding to bids where customers give us speciNic requirements
• Sell our services at low margins to compete with offshore vendors
• Get fewer opportunities to do the work we’re good at and enjoy – real product design and
development
• Get blamed when our customer’s ideas fail
15 @gajlof, gaine.se

16. Idea Brief
Our big idea: Create Lists: a simple ubiquitous mobile app
We believe that if we create a simple consumer mobile
app that we’ll be able to demonstrate our strong ability
to design and build simple, valuable applications.
This simple mobile app will help give our company
attention in the marketplace.
As a consequence, our target customers seek us out to
duplicate the success we’ve had with our product but on
their behalf.
Everyone wins.
16 @gajlof, gaine.se

17. 17

18. Proto-personas
18

19. small business users couples and families habitual list makers and note takers
Proto-personas for these 3 type
of users and customers
19 @gajlof, gaine.se

20. 20

21. 21

22. MVP
22
Pic from http://blog.crisp.se/2014/06/02/martinchristensen/en-guide-till-minimum-viable-products