No video

User Story Mapping Tutorial (How to create, read, and use story maps)

  Рет қаралды 2,243

Mountain Goat Software

Mountain Goat Software

Күн бұрын

Пікірлер: 16
@ianbabelon8259
@ianbabelon8259 Ай бұрын
As UX researcher and domain expert, I find user story maps an interesting type of artefact -- somewhat different from user journey maps in that they are perhaps more product- and dev-centric. I'm learning about Object-Oriented UX concurrently, which focuses on mapping all relevant 'objects' prior to mapping interactions and steps in user flows. OOUX might come in before user story maps or even user journey maps, and seems useful in combining goal-directed design approaches (possibly Jobs to be done as well?) with observational research about what users actually do and really need. This video is really useful in helping me to better understand how my colleagues who are more technical and product operations-focused go about building products, and how I can best feed UX research insights accordingly. Many thanks! ⭐
@MountainGoatSoftware
@MountainGoatSoftware Ай бұрын
You're welcome! I'm glad you find a lot of value from it. Knowing some UX design will certainly help enhance the story mapping process (you'll be able to provide more insight into user interactions and needs), but it isn't a prerequisite. The focus of story mapping is on understanding the sequence of user actions and identifying gaps or missing information, which you can do without having a deep knowledge of the UX design. So I'd caution you about mapping out every object before coming into a Story Mapping session.
@michaelwagener1411
@michaelwagener1411 Ай бұрын
Thanks Mike - as always a great video. Concise, relevant and intuitive - what's not to like. I shall share it immediately with my team, and the organisation that I work with.
@MountainGoatSoftware
@MountainGoatSoftware Ай бұрын
Thanks, Michael. I appreciate it.
@thx5001
@thx5001 Ай бұрын
This was a revelation in story mapping and I will use this with my new team. Keep up the good wlork
@MountainGoatSoftware
@MountainGoatSoftware Ай бұрын
I appreciate that. Thanks.
@luisvaz92
@luisvaz92 Ай бұрын
Always getting insights from these videos.
@MountainGoatSoftware
@MountainGoatSoftware Ай бұрын
Thank you.
@K-Killerzz
@K-Killerzz Ай бұрын
Thanks, Mike, I would like to ask in case we have multiple cases, how do we visualize on story map? And do we treat backbone as Epic? If yes for the incremental it means the epic done when all activities finish or mvp is release? In case mvp release but epic still have activity it means it never end?
@MountainGoatSoftware
@MountainGoatSoftware Ай бұрын
In a story map, multiple cases are visualized by placing stories across the grid to show the sequence in which they'll happen and down the grid to show alternatives. If there are multiple ways to achieve the same goal, those alternatives would be stacked vertically. The backbone isn't necessarily treated as an epic. The backbone represents the new or improved functionality users need and can be thought of as the topmost narrative in the story map. An epic isn't considered completed when the MVP is released. The MVP represents a subset of the functionality that delivers value early, but the epic may still have additional activities that need to be completed in subsequent iterations. So, if the MVP is released but the epic still has activities, it means that the epic is not yet complete. The remaining activities will continue to be worked on in future iterations until the epic is fully realized.
@ed8574
@ed8574 Ай бұрын
Hi Mike, if the product has several types of users and they have different experiences, do you recommend to create several story maps?
@MountainGoatSoftware
@MountainGoatSoftware Ай бұрын
Great question. I'd start out with one map but would very willingly create a second if needed. Sometimes the differences can be minor (but important). I'm thinking about the check out process on Amazon for prime vs. non-prime members. If 80% of that is the same I'd stick with one map (for simplicity) and just draw a little symbol on the cards that differ (or use a different color). But if the users are very different (normal user vs sys admin or such) start with separate maps.
@ed8574
@ed8574 Ай бұрын
@@MountainGoatSoftware that's great! Thanks a lot! I appreciate it
@MountainGoatSoftware
@MountainGoatSoftware Ай бұрын
@@ed8574 You're welcome
@ajaygovinds
@ajaygovinds Ай бұрын
Thanks for the question and for the answer. Recently I was finding it very difficult to get some expert answer on this specific question. Thank you once again 🙏🏻.
@MountainGoatSoftware
@MountainGoatSoftware Ай бұрын
@@ajaygovinds You're welcome.
Agile Epic, User Story, and Feature: Do Names Matter?
7:10
Mountain Goat Software
Рет қаралды 28 М.
黑天使遇到什么了?#short #angel #clown
00:34
Super Beauty team
Рет қаралды 42 МЛН
Please Help Barry Choose His Real Son
00:23
Garri Creative
Рет қаралды 18 МЛН
Walk through a User Story Map Example with Mike Cohn
6:15
Mountain Goat Software
Рет қаралды 1,6 М.
Job Stories vs User Stories: What's the Difference?
8:38
Mountain Goat Software
Рет қаралды 3,3 М.
Business Analyst - How to write Technical and Functional user stories
15:11
Business Analyst REAL-TIME Training
Рет қаралды 8 М.
User Story Mapping 101 - How to Create a USER STORY MAP
16:35
Online PM Courses - Mike Clayton
Рет қаралды 10 М.
SPIDR: 5 Ways to Split User Stories & Bring Any Story Down to Size.
8:23
Mountain Goat Software
Рет қаралды 9 М.
User Story Mapping using ThoughtFlow
9:05
ThoughtFlow
Рет қаралды 16 М.
A User Story Mapping Example with David Hussman
6:50
CardBoard
Рет қаралды 15 М.
Definition of Done vs Acceptance Criteria: What's the Difference?
4:42
Mountain Goat Software
Рет қаралды 23 М.
TECHNICAL STORIES DON'T WORK
20:55
Continuous Delivery
Рет қаралды 41 М.
What Are Product Goals & When Do Product Owners Create Them?
4:52
Mountain Goat Software
Рет қаралды 509