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.
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.
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 :)
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.
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.
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!
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.
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
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
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?
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.😆
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
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".
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?
Hey, we know. Sorry about that. We did what we could to improve that recording, you can see the version with better audio here: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-ISi0D16PmzI.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: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-ISi0D16PmzI.htmlsi=usTv0klocsUTtgB5 We learned, our newer videos (and the ones coming up) sound better :)
I know, was one of our early ones, we screwed that up. There is a version with better audio here: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-ISi0D16PmzI.html
I know, it was our first video and we screwed up the audio. There is a better version here ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-ISi0D16PmzI.html
