This video is slightly longer than the rest (i.e.: 20+ minutes) but it provides a very detailed explanation to put the technique into use. A very well-worth 20 mins spent on an evening.
The fact that the example here is not related with software makes it more interesting! stuff can be applied on practical life or any goal! this is gold, thank you Mr. BeanStalk!
This is super underrated! Very useful to see how user story mapping is applied in agile development. I kinda wished personas were tied to the examples you gave, but i figured that would narrow down the scope.
So So helpful! I liked that he explained and demonstrated the difference between increment and iteration. I see these two entities getting confused throughout Agile methods.
Thanks so much for going through an actual example from start to finish. I learn best by example and it was difficult finding a resource that breaks things down as well as this video did. Making my journey studying UXUI a little easier :)
Wow !!! Thank you for all your explanations !! I've learned what is exactly a story mapping and the morning routine is a perfect example to illustrate that !! I can't imagine how much time did you spend to make this video, but I can tell you that you made a great work, so helpful for lot of people.
Really, Really helpful explanation!!! I really appreciate the simplicity of it all, but at the same time, the time and effort put into making this video and creating a script
Really good video! Very insightful! I had to giggle at the morning gardening comment. That is something I do when I re-pot my plants etc. It's the perfect time of day since it's not too hot yet. The air is fresh and cool.
Great video! I found the video to be very helpful in understanding User Story Mapping, and it gave me valuable insights on how to implement it effectively for my team.
I can only back that. You should do more of these videos to propel your channel upwards. The level of information and how you convey them - incl hunour for enjoyment- are just really perfect. Thanks
thanks BUT I expected and needed a real-world example of the user story mapping for a real business case. but thanks so much for this simple explanation
Love this video, visualizing the workflow and using examples makes it much easier to understand. btw OP might want to consider shaving as a higher priority for his morning routine.😆
I really like this video, though these ideas aren't new to me. For someone who hasn't done this sort of organization of ideas it can be very helpful. Where it isn't complete (another video would be nice) is the same, but in the context of a software project. What are the many issues a project leader or architect needs to have on the sticky notes? What are the chronological sequence steps? How can one ensure the final product can be about the 1st priority things, yet have spacers for all other things which are likely to be incorporated later?
How to create a story map for an app who's backend is on web and frontend is mobile (android + ioS) + Web . How I can manage multiple release versions across multi platforms?
Hi thanks for the video. I do npt understand how to fit this to sprint planning. Do these tasks become user stories when you add them to a sprint? I see that you see releases but not what can be fit into a sprint? A release can be done in several sprints. What about user story splitting in case it is too big to do in 2 weeks?
Hello Alex, you're right when you say a release ( like the MVP ) can take several sprints. I understand story mapping is mainly to have a common understanding of the priorities. and then to create a big picture ( size and complexity ) remember that we can do story mapping for kanban. Therefore we do not have sprints. Also, user stories are one of the most recent types of product backlog items. my understanding is that a user story becomes an epic user story when it does not fit in one sprint. since we can not commit to completing a full epic user story in a sprint becomes advantageous to split it into smaller pieces so we still can show progress frequently.
In a Planning, the user story map will be useful to bring focus. For instance, a PO with whom I worked used her User Story Map in both the Planning and the Review. It helped her to quickly give context and focus. She at the Review: "We are here because of this (zooms out to see the full picture). We are currently focusing on this (zooms in to the release). We will talk about this (zooms in to the relevant items)". Stakeholders were always grateful that she took the 2 min to "bring them in".
So, love the concept of story mapping. However, the main issue to use is practicality. 99% of the teams I 've worked with use an electronic tool e.g. jira, devops, rally etc. No way they will maintain two sources of information, especially when lots of stories; and so one of the sources becomes quickly out of date. Suggestion?
Agree, multiple sources of information is impractical. You have some options though: 1) Separate Product Backlog and Sprint Backlog tools Keep the product backlog in a user story map in your tool of choice (I like Miro for the moment). When an item becomes priority and is picked up by the team in the Sprint, create it in Jira (which becomes your Sprint backlog tool), and then it continues its life-cycle there. You just update the story map to reflect when the item is delivered 2) Find tools that integrate Miro has a jira integration, for example, so you could use cards in a user story map (in Miro) and those cards are connected to Jira tickets help.miro.com/hc/en-us/articles/360017572434 3) User story map as Product Owner roadmap tool, JIRA/devops for the short-term backlog (next release) In this option you use the user story map in your tool of choice (e.g. Miro) but mainly for higher level roadmapping. So your items in the story map are larger (2-8 weeks of work). And you use that to prioritize the work and all the other beauties of user story mapping. And then when an item becomes high priority (i.e. coming up soon for the team to work on) you create the high-level item as an "epic" in jira, and then have the team split that into all the smaller items they have to deliver to achieve that "big feature". So in this scenario you use the user story map for prioritizing items of a higher level of granularity. And you use Jira/devops for splitting down those bigger items that made it into the current release we're working on. There are probably other options, these are some I frequently use with clients. Hope this helps
Hey, we know. Sorry about that. We did what we could to improve that recording, you can see the version with better audio here: th-cam.com/video/ISi0D16PmzI/w-d-xo.htmlsi=dK9Vwla1UR2KldF8
Thanks for the feedback. We know. It was one of our earlier videos and we screwed up. There is an updated version of this video with better audio here: th-cam.com/video/ISi0D16PmzI/w-d-xo.htmlsi=usTv0klocsUTtgB5 We learned, our newer videos (and the ones coming up) sound better :)
This video is slightly longer than the rest (i.e.: 20+ minutes) but it provides a very detailed explanation to put the technique into use. A very well-worth 20 mins spent on an evening.
I have seen PM explainer but nothing as crystal clear as this to handle the reality of chaos.. thanks BeanStalk so good!
The fact that the example here is not related with software makes it more interesting! stuff can be applied on practical life or any goal! this is gold, thank you Mr. BeanStalk!
This is super underrated! Very useful to see how user story mapping is applied in agile development. I kinda wished personas were tied to the examples you gave, but i figured that would narrow down the scope.
Best video I saw on internet for user journey mapping
So So helpful! I liked that he explained and demonstrated the difference between increment and iteration. I see these two entities getting confused throughout Agile methods.
Thanks so much for going through an actual example from start to finish. I learn best by example and it was difficult finding a resource that breaks things down as well as this video did. Making my journey studying UXUI a little easier :)
really great video, lots of shorter videos are not explaining the method in detail, but this will really help me for my master thesis. thanks!
Great video! Must watch if you want to understand story mapping. You will learn how to explain it to your grandmother!
this one of the best videos i've seen explaining user story mapping, thanks man !!
Thanks so much for sharing! Been trying to wrap my head around this all day - and this just made everything click.
Wow !!! Thank you for all your explanations !! I've learned what is exactly a story mapping and the morning routine is a perfect example to illustrate that !! I can't imagine how much time did you spend to make this video, but I can tell you that you made a great work, so helpful for lot of people.
Best video for being introduced to agile approaches. Thanks!
One of the best video in Product management
Really, Really helpful explanation!!!
I really appreciate the simplicity of it all, but at the same time,
the time and effort put into making this video and creating a script
Great video! Super clear explanations and good examples. Thank you so much for sharing it.
This is the best video I've seen on story mapping so far. You're amazing 🤩. Thank you !!!
Really good video! Very insightful!
I had to giggle at the morning gardening comment. That is something I do when I re-pot my plants etc. It's the perfect time of day since it's not too hot yet. The air is fresh and cool.
Amazing pedagogie!! Super actionable tutorial!!
Best video i have come across on agile.
You are an awesome teacher. 🤗🤗🤗
pretty cool way to explain it! (: I loved how you mixed the drawing with the actual example
U showed full creativity here .
Thanks for making Story mapping so interesting .. ❤️👍
So cool!!! I now understand the concept of the User Story Mapping and understand also why my intent of a “perfect” morning routine never happens!!!
Thanks a lot for your fluent and beautiful way of explaining and demonstraing ideas.
Hope to see more.
One of the best video I have seen.. took me a lot of time to find a best video to understand this concept very clearly 🙏🙏
Awesome Bean! Helps so many POs!
Great explanation of concept and example. Time to practice
Great video! I found the video to be very helpful in understanding User Story Mapping, and it gave me valuable insights on how to implement it effectively for my team.
Great way of explaining!
I have clicked on this by mistake but I like it. I think you should keep the 10 minutes length as standard.
I love this Agile methodology Sample it’s really Awesome
Thank you, I personally enjoyed it and found it really useful
I can only back that. You should do more of these videos to propel your channel upwards. The level of information and how you convey them - incl hunour for enjoyment- are just really perfect. Thanks
This kind of content is always free :)
This is so practical ❤
Thanks a lot. It is easy to understand. ❤
Very helpful thank you so much for making the topic so simple and easy to understand
Please make more videos on agile 🙏🙏🙏
Excellent presentation
thanks BUT I expected and needed a real-world example of the user story mapping for a real business case. but thanks so much for this simple explanation
Great video, Man! Found it easy to follow and the explanation was great
i love this!
Very useful, thanks!
Great video, great example and great content. Thank you so much!
Love this video, visualizing the workflow and using examples makes it much easier to understand. btw OP might want to consider shaving as a higher priority for his morning routine.😆
haha :) The real question would be then what should I de-prioritize? Shower? Breakfast? Or you want me to wake up earlier???
great video!
Very, very cool way to explain it. Great video, thank you
This video is just perfect!
helped a lot to clarify the concepts for me thanks a lot
Thanks a lot this is really helpful especially the real life example 🙏
Great explanation
Great explanation, would be nice to mention specific tools which are best to put such map into
We at Agilar love using either sticky notes on a wall or Miro.
We like Miro
hats off. thank you
Thanks!! You did it great!
thank you so much. this is so useful
Can you go into the TH-cam edit studio and boost the audio please as the volume is very low. Look into the lens.
I really like this video, though these ideas aren't new to me. For someone who hasn't done this sort of organization of ideas it can be very helpful. Where it isn't complete (another video would be nice) is the same, but in the context of a software project. What are the many issues a project leader or architect needs to have on the sticky notes? What are the chronological sequence steps? How can one ensure the final product can be about the 1st priority things, yet have spacers for all other things which are likely to be incorporated later?
great explanation, thx
Please do the video again WITH VOLUME so I can hear it. Thank you.
Thanks for the video, good example.
The "put on radio" task under the "food" step is triggering me. ;)
How to create a story map for an app who's backend is on web and frontend is mobile (android + ioS) + Web .
How I can manage multiple release versions across multi platforms?
What part of the day in scrum does user stories take place ?
Hi thanks for the video. I do npt understand how to fit this to sprint planning. Do these tasks become user stories when you add them to a sprint? I see that you see releases but not what can be fit into a sprint? A release can be done in several sprints.
What about user story splitting in case it is too big to do in 2 weeks?
Hello Alex, you're right when you say a release ( like the MVP ) can take several sprints.
I understand story mapping is mainly to have a common understanding of the priorities. and then to create a big picture ( size and complexity )
remember that we can do story mapping for kanban. Therefore we do not have sprints.
Also, user stories are one of the most recent types of product backlog items. my understanding is that a user story becomes an epic user story when it does not fit in one sprint. since we can not commit to completing a full epic user story in a sprint becomes advantageous to split it into smaller pieces so we still can show progress frequently.
In a Planning, the user story map will be useful to bring focus. For instance, a PO with whom I worked used her User Story Map in both the Planning and the Review. It helped her to quickly give context and focus. She at the Review: "We are here because of this (zooms out to see the full picture). We are currently focusing on this (zooms in to the release). We will talk about this (zooms in to the relevant items)". Stakeholders were always grateful that she took the 2 min to "bring them in".
With which software did you create this video please? it's very interesting.Thank you.
Amazing!
Perfect!
great example....!!
So, love the concept of story mapping.
However, the main issue to use is practicality.
99% of the teams I 've worked with use an electronic tool e.g. jira, devops, rally etc.
No way they will maintain two sources of information, especially when lots of stories; and so one of the sources becomes quickly out of date.
Suggestion?
Agree, multiple sources of information is impractical. You have some options though:
1) Separate Product Backlog and Sprint Backlog tools
Keep the product backlog in a user story map in your tool of choice (I like Miro for the moment). When an item becomes priority and is picked up by the team in the Sprint, create it in Jira (which becomes your Sprint backlog tool), and then it continues its life-cycle there. You just update the story map to reflect when the item is delivered
2) Find tools that integrate
Miro has a jira integration, for example, so you could use cards in a user story map (in Miro) and those cards are connected to Jira tickets
help.miro.com/hc/en-us/articles/360017572434
3) User story map as Product Owner roadmap tool, JIRA/devops for the short-term backlog (next release)
In this option you use the user story map in your tool of choice (e.g. Miro) but mainly for higher level roadmapping. So your items in the story map are larger (2-8 weeks of work). And you use that to prioritize the work and all the other beauties of user story mapping. And then when an item becomes high priority (i.e. coming up soon for the team to work on) you create the high-level item as an "epic" in jira, and then have the team split that into all the smaller items they have to deliver to achieve that "big feature". So in this scenario you use the user story map for prioritizing items of a higher level of granularity. And you use Jira/devops for splitting down those bigger items that made it into the current release we're working on.
There are probably other options, these are some I frequently use with clients.
Hope this helps
@@agilebeanstalk Also there's feature in the paid version of Miro that allows to connect to Jira for user story mapping so both of them are synced.
this is a great video but the volume is so low, so sharing this with my team as a group session is near on impossible :(
Can you explain how you transform high-level ideas outlined in a product roadmap into definitive items in a product backlog?
Thank you
meh... 😂
that was beautiful, great video!
👍
The audio is so low.
Hey, we know. Sorry about that. We did what we could to improve that recording, you can see the version with better audio here: th-cam.com/video/ISi0D16PmzI/w-d-xo.htmlsi=dK9Vwla1UR2KldF8
Great stuff, wish you hadn't used the exact example Jeff has used.
The audio is so low I literally can't hear what is being said
Yeah, we messed that up on this one. There is a better audio version here th-cam.com/video/ISi0D16PmzI/w-d-xo.html
@@agilebeanstalk That is great - thanks so much!
🤙🤙🤙🤙
I am really sorry but the voice level is so low...
Thanks for the feedback. We know. It was one of our earlier videos and we screwed up. There is an updated version of this video with better audio here: th-cam.com/video/ISi0D16PmzI/w-d-xo.htmlsi=usTv0klocsUTtgB5
We learned, our newer videos (and the ones coming up) sound better :)
Is this music from a video game? Swear I'm hearing Nintendo's Pikmin soundtrack Lol
'Process yesterday's curry' 🤣🤣🤣🤣🤣
With all those things suggested to accomplish I now know why I'm disshoveled.
Very low voice
dude missed out showering during the iteration
Your volume is way too low
Sound is terrible..content seem okay
I know, was one of our early ones, we screwed that up. There is a version with better audio here: th-cam.com/video/ISi0D16PmzI/w-d-xo.html
Gardening 😂
stupidity …. You changed definition of velocity and to make your point, recorded a hour long session… seriously, what’s wrong with you guys
sorry, what?
I'm so bored
my god, speak up and a microphone
I know, it was our first video and we screwed up the audio. There is a better version here th-cam.com/video/ISi0D16PmzI/w-d-xo.html