{"id":24480,"date":"2024-12-10T14:53:25","date_gmt":"2024-12-10T19:53:25","guid":{"rendered":"https:\/\/oshara.ca\/?p=24480"},"modified":"2024-12-10T15:21:56","modified_gmt":"2024-12-10T20:21:56","slug":"what-is-user-story-mapping","status":"publish","type":"post","link":"https:\/\/oshara.ca\/en\/what-is-user-story-mapping\/","title":{"rendered":"What is User Story Mapping and How It Can Help Your Development Process?"},"content":{"rendered":"\n

Have you ever found yourself in a situation where you have an elaborate idea about a business project, but you just have too much information and don\u2019t know where to start from?<\/strong><\/p>\n\n\n\n

This is common in creating everything, from making websites and developing software solutions, to building ceramics out of clay.<\/p>\n\n\n\n

Of course the more complex the final product is, the harder it is to make it.<\/strong> This is where User Story Mapping comes in handy.<\/p>\n\n\n\n

You have surely seen a scene in crime movies where they have this big dashboard and on it are faces of people that are connected to the crime. Below every connection, there is text explaining how they are connected and what they have done in the case.<\/p>\n\n\n\n

Well User Story Mapping works the same way, only it\u2019s a bit more complex.<\/p>\n\n\n\n

What is User Story Mapping?<\/h2>\n\n\n\n

User Story Mapping is a visual representation of how a product or a software is developed <\/strong>through stages. It\u2019s similar to a road map, but it\u2019s more flexible and it allows for developing of different parts at different speeds, which in product or software development<\/a> is very important because it saves time and money.<\/p>\n\n\n\n

It\u2019s called User Story Mapping because each step is written from the perspective of the user,<\/strong> like entering a password, or uploading a picture. Something that a user does and that action is described and inserted into the overall story\/development of the project.<\/p>\n\n\n\n

\"User
User Story Mapping for checking an email<\/figcaption><\/figure>\n\n\n\n

Here you can see how a typical User Story Map looks like. In User Story Mapping, the horizontal axis (in blue) shows the steps a user takes when using a product,<\/strong> like the process from beginning to end. And we can make it into a narrative if we add \u201cthen\u201d after each step. So you open your browser, THEN you go to your email website, THEN you enter your credentials\u2026<\/p>\n\n\n\n

The vertical axis lists the tasks or features for each step,<\/strong> with the most important ones at the top. We can make a narrative of each vertical step with adding the word \u201cor\u201d. So you go to your email website by typing the address directly OR clicking on the address that is bookmarked previously, OR finding it thought a Google search.<\/p>\n\n\n\n

These two parts make it easy for teams to see the big picture, plan their work,<\/strong> and focus on what\u2019s most helpful for the user at each step. So the teams can decide what is the minimum that they should do to get the MVP – the Minimum Viable Product.<\/p>\n\n\n\n

The Minimum Viable Product is like the bare minimum of your app or product<\/strong> that you can sell to the customer. For example, if you are making a cup out of clay, the MVP would be just a tiny vessel made out of clay that can store water and not leak.<\/p>\n\n\n\n

\"MVP
MVP – Minimum Viable Product of the above mapping<\/figcaption><\/figure>\n\n\n\n

The above is a representation of the MVP steps to check your email. We minimize the number of steps and make it as simple as possible, but still being functional so you can reach your final goal<\/strong>, to check your email.<\/p>\n\n\n\n

Now imagine all of this applied to building a complex e-store app. You want it to have many features, many ways to pay and to choose for different types of delivery. But you must start with a very first simple app where the user will be able to just simply buy one of your product and choose one shipping and be happy with the purchase.<\/p>\n\n\n\n

And with time you will be able to add more features,<\/strong> more ways to buy. More ways to look at the product, in 3D or with more pictures. You will be able to make the service better, but this first version will be your MVP – Minimum Viable Product.<\/p>\n\n\n\n

User Story Mapping vs. Waterfall <\/h2>\n\n\n\n

To understand better User Story Mapping, you need to know that before it there was an approach in creating software and products called Waterfall.<\/p>\n\n\n\n

Waterfall was more rigid approach that went through creation phases<\/strong> that were before agreed on and didn\u2019t had a lot of flexibility or participation. It was easier to sell to investors because it had more simple and obvious frame, but it was rigid and bumped into problems during development.<\/p>\n\n\n\n

This all changed in 2001 when a group of 17 software engineers published the Agile Manifesto<\/strong> that called for a more flexible methodology of creating software with more participation from the team.<\/p>\n\n\n\n

Agile is a way of building software by making small improvements regularly.<\/strong> It focuses on working together as a team, talking to customers, and adjusting based on feedback. Instead of following a strict plan, the team works in short cycles, called sprints, to make progress. The goal is to get better results faster and make changes when needed, rather than sticking to a fixed plan.<\/p>\n\n\n\n

That same year, Jeff Patton introduced the User Story Mapping method<\/strong> in his book \u201cUser Story Mapping: Discover the Whole Story, Build the Right Product\u201d<\/a>. User Story Mapping is used to visually represent the agile approach to creating a product or a software solution. The book was an instant hit and it spread through software development like a wildfire.<\/p>\n\n\n\n

How Can User Story Mapping Help your Project?<\/h2>\n\n\n\n

User Story Mapping is useful in many aspects of product or software creation. It\u2019s almost impossible today to imagine developing an app without having a User Story Map that will outline the steps and the options available.\u00a0<\/p>\n\n\n\n

If you go into any software agency, you will see a dashboard that has a User Story Map drawn on it,<\/strong> because it\u2019s so crucial for efficient and timely development of software.\u00a0<\/p>\n\n\n\n

So main benefits of User Story Mapping are:<\/strong><\/p>\n\n\n\n

    \n
  • Cutting Costs & Efficiency:<\/strong> this might sound a bit controversial, but this is the bottom line of a good story mapping. Cutting cost means better efficiency in creating your software app or your product. It means having an MVP – minimum viable product ready for less money, which gives you better chances of getting your app out there.<\/strong> It means you need less investment, your investors will be able to see your vision and use your app, so you would be able to get even more investments down the line.<\/li>\n\n\n\n
  • Visualization:<\/strong> Visualization of how your product works from user perspective<\/strong> helps you to share that vision with your team and investors. Everybody get a feeling of what your app or product will do, and what steps users will take.<\/strong> It\u2019s hard to understand how important visualization of the whole process is until you get to the point to explain it to other people.\u00a0<\/li>\n\n\n\n
  • Prioritizing Features:<\/strong> User Story Mapping allows you to make a \u201cskeleton\u201d version of your software app or product and add whichever feature you think is important. It also keeps in perspective the other features that you will introduce in the next versions.<\/strong> For example, a decade ago, Google had an update (which today is totally normal for us) when suggestions started to pop us as you type your keywords, and that was a great update that made the search very fast and more convenient. Before that, you had to type out your whole search quarry and then type enter and then see the result. But because many query questions are not totally formed in our heads, you had to search Google multiple times to get what you wanted, now you usually do that with just one search.<\/li>\n\n\n\n
  • Improved Collaboration and Communication: <\/strong>Huge part of the improved efficiency that the Agile model and the User Story Mapping is giving you is the inclusivity and collaboration that takes place.<\/strong> Everyone who is working on the project is usually part of sessions where they brainstorm ideas. Having all of this participation and exchange of ideas makes the whole process much efficient, because you get exposed to ideas and ways of doing things you have never even thought of.\u00a0<\/li>\n\n\n\n
  • Accountability:<\/strong> Because User Story Mapping gives such a clear and efficient presentation of what should be done, it\u2019s very easy to delegate then these assignments to teams, and set estimated dates of completion. The Scrum method has this detailed<\/strong> where you put one piece of the job, one task, previously defined with the team, and have the developers finish it in 1-4 weeks time.<\/strong>\u00a0<\/li>\n<\/ul>\n\n\n\n

    There is a good overview in the video below:<\/p>\n\n\n\n

    \n