how to rob a bank: an overview of user story mapping - iiba msp · 2015-06-01 · story maps...
TRANSCRIPT
How to Rob A Bank:
An Overview of User Story Mappingpresented at IIBA Minneapolis/ St. Paul
Mike Stuedemann, PMP, PMI-ACP, CSP
Certified Scrum Professional & Agile Coach
http://collaborativeleadershipteam.com
@CoLeadTeam
Mike Stuedemann PMP, PMI-ACP, CSP
• 17+ years Information Technology -
traditional SDLC and Scrum/Agile
• Practicing Agile since 2007
• Certified Scrum Professional
• Active member in the Scrum Alliance
and the PMI-MN Agile Practitioner
Community
• Married with 3 Boys - based in
Andover, MN
Copyright 2015 Collaborative Leadership Team 2
User Story Mapping Agenda
• What’s a User Story?
• What’s the Problem?
• What’s a User Story Map and how can it help
me?
• “How to Rob a Bank” – A User Story Map
Exercise
• Wrap-Up
3Copyright 2015 Collaborative Leadership Team
What is a User Story?
• A User Story is a
requirement or
feature expressed
briefly from the user’s
perspective
• Describe who has a
particular need or
want, what that need
or want is and why
they need it
Copyright 2015 Collaborative Leadership Team 4
What is a User Story?
• A technique from Extreme
Programming
• Many using Scrum adopt
this technique for
capturing items on the
Product Backlog but
Scrum does not prescribe
this
• A note about the format
shown at the right
5Copyright 2015 Collaborative Leadership Team
What is a User Story?
• Stories are traditionally
written on note cards
• Cards may be annotated with
estimates, notes, etc.
• Details behind the story
come out during
conversations between
stakeholders, product owner
and team
• Acceptance tests confirm that
the story was coded correctly
Card
Conversation
Confirmation
Copyright 2015 Collaborative Leadership Team 6
What’s the Issue?
7Copyright 2015 Collaborative Leadership Team
The First Issue…
Copyright 2015 Collaborative Leadership Team 8
The Second Issue…
Copyright 2015 Collaborative Leadership Team 9
Story Maps
Activity 1 Activity 2 Activity 3 Activity 4
User Story User Story User Story User Story
User Story User Story User Story User Story
User Story User Story User Story User Story
User Story User Story User Story User Story
User’s Sequence in Time
Activitiesare
functional behaviors of the user
User Stories are narrative descriptions of the features needed by the user to perform those activities
Story Maps visualize the overall product, and thereby help to convey the “Big Picture”
10Copyright 2015 Collaborative Leadership Team
How to Create a Story Map
1. Discuss Activities associated with the Product /
Service
2. Sequence the Activities
3. Add Tasks (As Necessary)
4. Brainstorm and discuss User Stories
associated with the Activities
5. Shift the User Stories vertically based on their
business priority
11Copyright 2015 Collaborative Leadership Team
Story Map Example
Activities
Tasks
Higher PriorityUser Stories
Lower PriorityUser Stories
12Copyright 2015 Collaborative Leadership Team
Reference: www.agileproductdesign.com
The Benefits of a Story Map
• Provide Story Context
• Shows Relationship between Stories
• Make value delivery visible
• Allows for Ordering of Stories by Business Value
• Allows the identification of valuable product slice
13Copyright 2015 Collaborative Leadership Team
Reference: www.agileproductdesign.com
Story Maps – Allow us to “walk” Personas
through Features
Activity 1 Activity 2 Activity 3 Activity 4
User Story User Story User Story User Story
User Story User Story User Story User Story
User Story User Story User Story User Story
User Story User Story User Story User Story
User’s Sequence in Time
Soccer Mom
Millennial
Hacker • Walk each persona through the user sequence• Discover gaps in the user stories & how they support
the user activities
14Copyright 2015 Collaborative Leadership Team
Disclaimer
15Copyright 2015 Collaborative Leadership Team
Exercise: How to Rob a Bank
• The Setting: You are a self-organizing team planning to rob a bank
• Your Challenge:
– Create a User Story Map describing the necessary activities from the time you arrive at the bank until the time you leave the bank
• Guidelines:– Time box: 20 minutes
– Remember: Things can always change…
16Copyright 2015 Collaborative Leadership Team
Exercise: How to Rob A Bank – A Change in
Timing?
17Copyright 2015 Collaborative Leadership Team
Story-Mapping in the “Real World”
18Copyright 2015 Collaborative Leadership Team
A Reminder….
19Copyright 2015 Collaborative Leadership Team
“Remember: at the end of the day, your job isn’t to
get the requirements right – it’s to change the
world”
– Jeff Patton
How to Rob A Bank: An Overview of User
Story Mapping – Summary
• The purpose of a User Story is conversation, not a
document
• A flat list of User Stories does not provide context – it is
easy to lose site of the product being built and the
relationship of the Stories to one another
• User Story Maps are a tool to both facilitate conversation
and provide context
• Please don’t rob a bank
Copyright 2015 Collaborative Leadership Team 20
Questions
Copyright 2015 Collaborative Leadership Team21
Copyright 2015 Collaborative Leadership Team 22
Want to get the Slides? Engage in Witty Banter?
Provide Feedback (Accusations, Insults)?
Contact Mike at:[email protected]
@StuedeSpeaks
Copyright 2015 Collaborative Leadership Team 23