User Story Mapping Tutorial (How to create, read, and use story maps)
Вставка
- Опубліковано 2 сер 2024
- In this practical guide to how to create story maps, expert Mike Cohn offers a user story mapping tutorial, from what a story map is, to why story maps are helpful, to when teams create user stories.
You'll learn
* how to create a story map along two dimensions
* how to read a story map
* how teams can use story maps to understand their product users and requirements
* how to turn a story map into a product roadmap
Don't miss this opportunity to get free training in the essential agile skills of how to use, read, and create story maps.
Free Downloads
Story Map Template and Cheatsheet
www.mountaingoatsoftware.com/...
More User Story Training from Mountain Goat Software
On-demand user story training: www.mountaingoatsoftware.com/...
Instructor-led user story training: www.mountaingoatsoftware.com/...
Private Story Writing Workshops: www.mountaingoatsoftware.com/...
Whole Team Training Course: www.mountaingoatsoftware.com/...
Inside "User Story Mapping Tutorial (How to create, read, and use story maps)"
00:00 Get essential agile skills: use, read, and create a story map
00:55 What is a story map?
01:30 Example user story map
02:00 Introducing a second dimension to story maps
03:00 How to add priority to story maps
03:18 What is the backbone of a story map?
03:48 How to tame an out-of-control story map
04:24 Defining story mapping terms: step, activity and narrative
06:12 Two times to create a new story map
06:49 Should you create a story map for everything?
07:41 Who should participate in story mapping?
08:57 Turn a story map into a product roadmap
10:04 How to indicate multiple milestones on a roadmap
10:18 Why create story maps - and how to make yours robust
10:55 Why story maps are effective tools
Related Videos
What Are Job Stories?
• Job Stories vs User St...
Two Times to Use Job Stories vs User Stories
• When To Choose Job Sto...
User Stories, Epics, Themes
• Agile Epic, User Story...
Playlist: Writing Better User Stories
• How to Write Better Us...
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! ⭐
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.
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.
Thanks, Michael. I appreciate it.
This was a revelation in story mapping and I will use this with my new team. Keep up the good wlork
I appreciate that. Thanks.
Always getting insights from these videos.
Thank you.
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?
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.
Hi Mike, if the product has several types of users and they have different experiences, do you recommend to create several story maps?
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.
@@MountainGoatSoftware that's great! Thanks a lot! I appreciate it
@@ed8574 You're welcome
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 🙏🏻.
@@ajaygovinds You're welcome.