SlideShare a Scribd company logo
Iteration 10
      User Story Mapping
with Jon Labun & Steve Rogalsky
    Twitter hash tag #agilewpg
Jeff Patton
AGILE 2011
Why should you care




                AGILE 2011
Ron Jeffries & Chet Hendricks:
“Agile is simple, but it’s not easy”
Simple but not Easy
• Use self organizing teams … but people have
  competing interests

• Deliver greatest value … but each person
  defines value differently

• Break stories down to workable sizes … but
  sometimes you lose the plot!
User Story Mapping
User Story Mapping
Some Definitions
Some Definitions
User Activities
Some Definitions
User Activities

User Tasks
Some Definitions
User Activities

User Tasks




 User Stories
Some Definitions




                                     Priorities
User Activities

User Tasks




 User Stories
Some Definitions




                                     Priorities
Time

User Activities

User Tasks




 User Stories
Some Definitions




                                                Priorities
Time

User Activities

User Tasks




 User Stories




                                     Releases
Some Definitions




Project
Status
What can Story Mapping do for me?
How to do it?
1. Divide into groups of 3-5 people
2. Start by gathering “things people do” – the user tasks. Write
them down individually and then read them aloud to your group
   – Likely they start with a verb.
   – These are high level user stories called “User Tasks” (walking
     skeleton)
   – This forms your story map skeleton
3. Group them silently (simply because it is faster)
4. Name the groups and lay them out in order of time (left to
right)
   – These are called “User Activities” (backbone)
5. Add more detailed user stories below the main tasks
6. Prioritize top to bottom
7. Break into releases
How to do it?
smithcdau (@smithcdau)
11-08-11 2:12 PM
RT @shanehastie: @jeffpatton if you're arguing
about sequence it probably means it doesn't
matter. #Agile2011 #yam
User Story Mapping
Some Definitions (review)




                                                Priorities
Time

User Activities

User Tasks




 User Stories




                                     Releases
User Story Slices - Compose Email
User Story Mapping
User Story Mapping
Wrap-Up
• Make better decisions
• Increase your ability to deliver (interests &
  value)
• Allay fears of agile sceptics
Links
• Two articles from Jeff:
  – http://www.agileproductdesign.com/blog/the_ne
    w_backlog.html
  – http://www.agileproductdesign.com/writing/how
    _you_slice_it.pdf
• Online User Story Mapping:
  – http://www.cardmapping.com

More Related Content

PPTX
User Story Mapping
PPTX
User Story Mapping
PPTX
User Story Mapping Workshop
PPTX
User Story Mapping
PDF
AgileCamp Silicon Valley 2015: User Story Mapping
PPTX
Storymapping workshop for CHI Belgium
PPTX
User story Mapping - A Brief Primer
PDF
User story mapping
User Story Mapping
User Story Mapping
User Story Mapping Workshop
User Story Mapping
AgileCamp Silicon Valley 2015: User Story Mapping
Storymapping workshop for CHI Belgium
User story Mapping - A Brief Primer
User story mapping

What's hot (11)

PDF
User Stories and User Story Mapping by Jason Jones
PDF
Story mapping workshop - NUXCamp 2015 Leeds
PDF
User Story Mapping-Hands-On // UX-DAY MASTERCLASS
PPTX
Story Mapping in Practice
PPTX
Integrating Axure Into Your Design Process
PPTX
Development slam 2017
PPT
Complexinterfaces
PDF
Agile Prototyping Best Practices
PDF
OOUX + API design: Love at first "site"
PDF
PyTexas 2014
PDF
WORKSHOP: Object Oriented UX for Responsive Design
User Stories and User Story Mapping by Jason Jones
Story mapping workshop - NUXCamp 2015 Leeds
User Story Mapping-Hands-On // UX-DAY MASTERCLASS
Story Mapping in Practice
Integrating Axure Into Your Design Process
Development slam 2017
Complexinterfaces
Agile Prototyping Best Practices
OOUX + API design: Love at first "site"
PyTexas 2014
WORKSHOP: Object Oriented UX for Responsive Design
Ad

Viewers also liked (20)

PPTX
User Story Mapping in Practice
PDF
Project inception mke agile june 2013
PPTX
Understanding the Disconnect Between Collaboration Tools and Business Goals
PPTX
Mind map final version
PPTX
Agile Velocity Story Mapping Session from Product Camp Austin 11 #PCATX
PPTX
Agile Application Lifecycle Management 6.2.2014
PDF
Agile Project Management for Elearning – ATD TechKnowledge 2017
PPTX
Mapping Out Agile Product Management - Agile Portugal 2011 - Mack Adams
PPTX
Agile & UX What changes and other C.R.A.P.
PDF
User Story Mapping
PDF
Successful Agile Transformation - The NCS Story
PDF
Leading Agile Product Discovery
PDF
AWB - 06 - Agile Planning, Release and Sprint
PDF
User Story Mapping
PPTX
Analysis In Agile: It's More than Just User Stories
PDF
Story Maps in practice
PPTX
Agile Requirements Decomposition
PPT
Leadership Competency Model for Supervisors and Managers
PPTX
Task management system
PPT
Overview Of Competencies & Benefits and Uses of a Competency-Based System
User Story Mapping in Practice
Project inception mke agile june 2013
Understanding the Disconnect Between Collaboration Tools and Business Goals
Mind map final version
Agile Velocity Story Mapping Session from Product Camp Austin 11 #PCATX
Agile Application Lifecycle Management 6.2.2014
Agile Project Management for Elearning – ATD TechKnowledge 2017
Mapping Out Agile Product Management - Agile Portugal 2011 - Mack Adams
Agile & UX What changes and other C.R.A.P.
User Story Mapping
Successful Agile Transformation - The NCS Story
Leading Agile Product Discovery
AWB - 06 - Agile Planning, Release and Sprint
User Story Mapping
Analysis In Agile: It's More than Just User Stories
Story Maps in practice
Agile Requirements Decomposition
Leadership Competency Model for Supervisors and Managers
Task management system
Overview Of Competencies & Benefits and Uses of a Competency-Based System
Ad

Similar to User Story Mapping (20)

PDF
Exploring UX Practices 4 Product Development Agile2012
PDF
Exploring ux practices 4 product development agile2012
PDF
Agile Scrum Overview
PDF
Agile gathering + guidelines stories
PDF
User Experience Design Fundamentals - Part 1: Users & Goals
PDF
User Experience Design Fundamentals - Part 2: Talking with Users
PPTX
Mural: Build Experiences Not Features
PPTX
Making the Transition to Agile: what we did, what worked, and what we learned
PDF
Agile comparison with requriement approaches
PPT
306 belmont ssp08agileit
PDF
AT2012_Pune_UserStories_BhawanaGupta
PDF
Design Simple but Powerful application
PDF
User Stories Applied
PDF
SharePoint Exchange Forum - How to Make a SharePoint Site Intuitive
PPTX
Story maps and personas an intro
PDF
Sdec11 when user stories are not enough
PDF
T bunio active-architecture
PPTX
Using Agile to move from info centric to user centric
Exploring UX Practices 4 Product Development Agile2012
Exploring ux practices 4 product development agile2012
Agile Scrum Overview
Agile gathering + guidelines stories
User Experience Design Fundamentals - Part 1: Users & Goals
User Experience Design Fundamentals - Part 2: Talking with Users
Mural: Build Experiences Not Features
Making the Transition to Agile: what we did, what worked, and what we learned
Agile comparison with requriement approaches
306 belmont ssp08agileit
AT2012_Pune_UserStories_BhawanaGupta
Design Simple but Powerful application
User Stories Applied
SharePoint Exchange Forum - How to Make a SharePoint Site Intuitive
Story maps and personas an intro
Sdec11 when user stories are not enough
T bunio active-architecture
Using Agile to move from info centric to user centric

More from Steve Rogalsky (14)

PPTX
Story Maps: Episode IV - A New Slice
PPTX
Retrospectives: from Whatever to Wow
PPTX
Agile in Winnipeg:.a retrospective
PPTX
Your Design is only Mostly Dead
PPTX
Trends in Agile Software
PPTX
A Guide to Lean Coffee
PPTX
Silent Brainstorming: A Guide To Using Post-its
PPTX
The Silence of Agile
PPTX
Agile101 Small Batches
PPTX
Multitaskers Anonymous
PPTX
User Story Workshop
PPTX
Moving Towards Zero Defects with Specification by Example
PPTX
Winnipeg Agile Users Group March 10 2011
PPT
Using Value Stream Mapping to make the case for Acceptance Test Driven Develo...
Story Maps: Episode IV - A New Slice
Retrospectives: from Whatever to Wow
Agile in Winnipeg:.a retrospective
Your Design is only Mostly Dead
Trends in Agile Software
A Guide to Lean Coffee
Silent Brainstorming: A Guide To Using Post-its
The Silence of Agile
Agile101 Small Batches
Multitaskers Anonymous
User Story Workshop
Moving Towards Zero Defects with Specification by Example
Winnipeg Agile Users Group March 10 2011
Using Value Stream Mapping to make the case for Acceptance Test Driven Develo...

Recently uploaded (20)

PPTX
Spectroscopy.pptx food analysis technology
PDF
NewMind AI Weekly Chronicles - August'25-Week II
PDF
Accuracy of neural networks in brain wave diagnosis of schizophrenia
PPTX
SOPHOS-XG Firewall Administrator PPT.pptx
PDF
Advanced methodologies resolving dimensionality complications for autism neur...
PDF
gpt5_lecture_notes_comprehensive_20250812015547.pdf
PDF
Diabetes mellitus diagnosis method based random forest with bat algorithm
PDF
Mushroom cultivation and it's methods.pdf
PPTX
Programs and apps: productivity, graphics, security and other tools
PDF
Encapsulation_ Review paper, used for researhc scholars
PDF
Architecting across the Boundaries of two Complex Domains - Healthcare & Tech...
PPTX
Tartificialntelligence_presentation.pptx
PDF
Approach and Philosophy of On baking technology
PDF
Getting Started with Data Integration: FME Form 101
PDF
Empathic Computing: Creating Shared Understanding
PPT
Teaching material agriculture food technology
PPTX
TLE Review Electricity (Electricity).pptx
PDF
Mobile App Security Testing_ A Comprehensive Guide.pdf
PPTX
Digital-Transformation-Roadmap-for-Companies.pptx
PPTX
cloud_computing_Infrastucture_as_cloud_p
Spectroscopy.pptx food analysis technology
NewMind AI Weekly Chronicles - August'25-Week II
Accuracy of neural networks in brain wave diagnosis of schizophrenia
SOPHOS-XG Firewall Administrator PPT.pptx
Advanced methodologies resolving dimensionality complications for autism neur...
gpt5_lecture_notes_comprehensive_20250812015547.pdf
Diabetes mellitus diagnosis method based random forest with bat algorithm
Mushroom cultivation and it's methods.pdf
Programs and apps: productivity, graphics, security and other tools
Encapsulation_ Review paper, used for researhc scholars
Architecting across the Boundaries of two Complex Domains - Healthcare & Tech...
Tartificialntelligence_presentation.pptx
Approach and Philosophy of On baking technology
Getting Started with Data Integration: FME Form 101
Empathic Computing: Creating Shared Understanding
Teaching material agriculture food technology
TLE Review Electricity (Electricity).pptx
Mobile App Security Testing_ A Comprehensive Guide.pdf
Digital-Transformation-Roadmap-for-Companies.pptx
cloud_computing_Infrastucture_as_cloud_p

User Story Mapping

  • 1. Iteration 10 User Story Mapping with Jon Labun & Steve Rogalsky Twitter hash tag #agilewpg
  • 4. Why should you care AGILE 2011
  • 5. Ron Jeffries & Chet Hendricks: “Agile is simple, but it’s not easy”
  • 6. Simple but not Easy • Use self organizing teams … but people have competing interests • Deliver greatest value … but each person defines value differently • Break stories down to workable sizes … but sometimes you lose the plot!
  • 13. Some Definitions Priorities User Activities User Tasks User Stories
  • 14. Some Definitions Priorities Time User Activities User Tasks User Stories
  • 15. Some Definitions Priorities Time User Activities User Tasks User Stories Releases
  • 17. What can Story Mapping do for me?
  • 18. How to do it? 1. Divide into groups of 3-5 people 2. Start by gathering “things people do” – the user tasks. Write them down individually and then read them aloud to your group – Likely they start with a verb. – These are high level user stories called “User Tasks” (walking skeleton) – This forms your story map skeleton 3. Group them silently (simply because it is faster) 4. Name the groups and lay them out in order of time (left to right) – These are called “User Activities” (backbone) 5. Add more detailed user stories below the main tasks 6. Prioritize top to bottom 7. Break into releases
  • 19. How to do it? smithcdau (@smithcdau) 11-08-11 2:12 PM RT @shanehastie: @jeffpatton if you're arguing about sequence it probably means it doesn't matter. #Agile2011 #yam
  • 21. Some Definitions (review) Priorities Time User Activities User Tasks User Stories Releases
  • 22. User Story Slices - Compose Email
  • 25. Wrap-Up • Make better decisions • Increase your ability to deliver (interests & value) • Allay fears of agile sceptics
  • 26. Links • Two articles from Jeff: – http://www.agileproductdesign.com/blog/the_ne w_backlog.html – http://www.agileproductdesign.com/writing/how _you_slice_it.pdf • Online User Story Mapping: – http://www.cardmapping.com

Editor's Notes

  • #8: Breakfast (Steve)Step 1: Generate tasksSplit up into groups of 3 to 5As individuals, think about your morning routine – the things you do.Write down each thing you do on one post-it note. Have everyone in your group use the same colour post-it for this exercise.Step 2: Read them outHave each person read their post-its out loud to the group and then place them in the middle of the table so that you can see all the post-its at once.Comments: Notice the similarities between your post-its and other peoples. Notice also that if you missed a few things, somebody else came up with the missing tasks. You probably all have things like “Brush Teeth”, “Get Dressed”, “Eat breakfast”. All starting with verbs.Step 3: GroupNow as a group, and without talking, move the post-its that are similar to each other closer to each other, and those that are not similar, move them farther apart. Those that are exact duplicates you can eliminate or put on top of each other.Step 4: Name the groupsYou should now have some distinct groups. As a group again, start labeling these groups with a different colour post-it. Just put the group name on top of the grouping.Step 5: Now re-arrange your groups in order of time from left to right. Put the group post-it at the top and the tasks below the group, but still in order left to right.(At this point, show a simple example)Overall comments:Your first user story map!The groups are called “User Activities” – this is the backbone of your applicationThe items below are called “User Tasks” – this is the walking skeleton of your application
  • #9: Breakfast (Steve)
  • #11: User Activities are things that users do towards achieving a particular goal.
  • #12: User Tasks are specific steps within an activity. Tasks by themselves do not move towards a goal, but are required components of an activity.
  • #13: User Stories are small end-to-end vertical slices of functionality that implement User Tasks.
  • #14: Not H/M/L, but top to bottom
  • #16: Goal: Release a minimum of one story in each column after the first two iterations.Why: Validate / Test (as per Jon above)
  • #18: For PM:For Developer:For QA:For Customer:For Architect:For Analyst (middle-up)For Quiet contributor:Deck of cards, pick 5 cards and make the best poker handBreakfast – power outage and you only have 15 minutes – what do you cut?
  • #21: We’re going to create a second map with some more detail and more relevance to software. You can move your old map out of the way.Practice – build your own MS Outlook competitor.Step 1: Generate tasksSplit up into groups of 3 to 5As individuals, think about your usage of your favourite e-mail toolWrite down each thing you do on one post-it note. Have everyone in your group use the same colour post-it for this exercise.Step 2: Read them outHave each person read their post-its out loud to the group and then place them in the middle of the table so that you can see all the post-its at once.Comments: Notice the similarities between your post-its and other peoples. Notice also that if you missed a few things, somebody else came up with the missing tasks. You probably all have things like “Send Email”, “Read Email”, “View Calendar”, “Create Contact”, etc.Again, all starting with verbs.Step 3: GroupNow as a group, and without talking, move the post-its that are similar to each other closer to each other, and those that are not similar, move them farther apart. Those that are exact duplicates you can eliminate or put on top of each other.Step 4: Name the groupsYou should now have some distinct groups. As a group again, start labeling these groups with a different colour post-it. Just put the group name on top of the grouping.Step 5: Now re-arrange your groups in order of time from left to right. Put the group post-it at the top and the tasks below the group, but still in order left to right.Overall comments:Your second user story map!Reminder:The groups are called “User Activities” – this is the backbone of your applicationThe items below are called “User Tasks” – this is the walking skeleton of your applicationNotice how fast you were able to create a reasonable outline for your whole application?Keep this map as we will be adding to it shortly. At this point we have no user stories.
  • #22: Goal: Release a minimum of one story in each column after the first two iterations.Why: Validate / Test (as per Jon above)
  • #23: Tell Wizard of Oz / Sneakernet storiesBest place to go out for beers near the convention centre (doesn’t scale, but…)Spreadsheets to input dataSecurity later (install only on secure machines for first release)
  • #24: In your user story map you should probably have a “Compose Email” or “Create Email” user task under the “Email Management” user activity or something similar. (if not, then what kind of e-mail have you been using?)We’re going to create the stories that go under that User Activity.Step 1: Generate tasksSplit up into groups of 3 to 5As individuals, think about creating an e-mail and write one user story (just the title, don’t worry about the rest) on each post-it. Slice each story thinly.Again, have everyone in your group use the same colour post-it for this exercise but use a different colour than the ones you have used so far.Step 2: Read them outHave each person read their post-its out loud to the group and then place them in the middle of the table so that you can see all the post-its at once.Again:Notice the similarities between your post-its and other peoples. Notice also that if you missed a few things, somebody else came up with the missing tasks. Step 3: GroupNow as a group, and without talking, move the post-its that are similar to each other closer to each other, and those that are not similar, move them farther apart. Those that are exact duplicates you can eliminate or put on top of each other.Step 4: PrioritizeInstead of naming our groups, this time we are just going to prioritize them top to bottom. The ones at the top will be created first and the others second.Think about the order that each piece would have to be built (again, reminder of the I in INVEST)If you are disagreeing about any story, feel free to split it again if you can.You can do this out loud.Overall comments:Again, notice how fast you were able to create a reasonable outline for your whole application? Has requirements gathering ever been this fast for you?You would repeat this for each activity and there are other requirements facilitation techniques to use like personas, scenarios, UX Design Studio, etc. These models are all inclusive models. They involve everyone and take advantage of all ideas without resorting to the trouble that is brainstorming or even writing down the correct interview questions in order to generate your high level scope and requirements.Do this with your customer!!!