8 Steps to create a user story Mapping

[Small series] on the Saturday to understand the user story map, small series and looked up some information, found the following this article on how to organize user story map planning articles, share to everyone. Also hope that if you have good practice, you can also leave a message to communicate.

Original address: http://winnipegagilist.blogspot.jp/2012/03/how-to-create-user-story-map.html

Thanks to Jeff Patton and others for their outreach, user story maps have become a popular approach in agile demand planning. User Story maps can turn your backlog into a two-dimensional map, rather than a traditional simple list. User Story maps address the following issues:

– Make it easier to see the full picture of your backlog
– Provides better tools for new feature filtering (grooming) and prioritization to help you make decisions
– Easy to use silent brainstorming mode and other collaborative methods to generate user stories
– Help you better iterate incrementally, while ensuring that early releases validate the overall architecture and solution
– Provides a better alternative to traditional project planning
– Helps motivate discussion and manage project scope
– Allows you to plan projects from multiple dimensions and ensure that different ideas are accepted

8 Steps to create a user story map

2. 3-5 people who are very familiar with the product are called in. 3-5 people sound like a magic number, actually yes. Because fewer people mean you can't get enough advice, and more people will reduce the efficiency of meetings because of discussion and coordination.
4. Using silent brainstorming, let everyone write down the "What to do" that they think is important on the sticky note paper, which is the user task. Everyone uses the same color notes to write their own user task descriptions, and this stage does not talk to each other. Once everyone has basically completed the preparation, let everyone take turns aloud to read their own content, and put all the sticky note paper on the desktop, if there is duplicate content can be omitted:
   1. Depending on the size of your product, this process can take up to 3-10 minutes, and you can watch your behavior to see if you need to stop.
   2. Basically every note starts with a verb, such as sending an email, creating a contact, adding a user, and so on.
   3. These notes form a first-level user story, and Jeff Patton is called the user task, which makes up the "Walking Skeleton" (The Walking Skeleton) part of the user story map.
   4. At this point you can prompt the participant: we have only a little time to complete the collection process of the requirements, and some of the content you may not think, while others help you think of.
6. Then, let Everyone group all the notes on the desktop, divide similar tasks into groups, and other similar
   1. This process is best done in silent mode, as it will be quicker to do so. If duplicate content is found, skip
   2. Basically grouping will be easy to complete
   3. At this point we also observe the behavior of each person to determine whether they have finished, basically this process takes 2-5 minutes
8. Select a different color of the note, name each group, and paste it in the top of each group of notes
10. Sort the notes of these sub-groups, usually in the order of the user to complete the operation, from left to right display
    1. If you can't decide the order, then the order may not be that important (obvious).
    2. This set of notes, Jeff Patton, is called user activity (users activities)
    3. At this point your map should resemble
       
12. Now, follow the "walking skeleton" user behavior line to start telling the user story, making sure you don't miss any user behavior and user tasks. This is usually told by the organizer, and other people make comments, even allowing the end user to participate in the discussion.
14. At this point, we have completed the basic framework of the user story map, you can add a more detailed user story under each user task Stories. It is still advisable to use the silent brainstorming mode to generate the first round of user stories, and to assist with this process, such as persona and scenario. Once you have completed the creation of your user story, you can begin to define your release plan (releases) .
    1. Generally I'm used to selecting only 2-3 user stories for each user task in the first release. This will help you prioritize and scope.
    2. Basically we don't have to use the standard syntax of user stories (as a ... To write these stories, because each note is in a specific location on our map, and it's easy to identify the scene and the character it's in.
16. Finally, the decomposition of all user stories for the first release ensures that our first release is as small as possible, and basically you need to ensure that the first version of your product is released after 1-2 iterations.

User Story Plot example

Here is a user story map of an e-mail system

– The second line contains "What you need to do in the e-mail system", including: writing a message, sending an email, creating an appointment, and so on.
– These things are grouped in the first line
– The first line of the yellow sticky note contains a minimized user story, such as: Write a message that includes only the sender, recipient, title, content, and send Cancel button. Other, such as support rtf,html format, add attachments, from the communications department to get contact e-mail address, etc., are not on this line, put in a more down note.
– Smaller blue and orange notes on yellow sticky notes indicate different states, such as: Blue is done, Orange is in progress (WIP), so you can see the progression of the project

Now if we focus on the yellow sticky note of the first line from left to right, we can make sure that a mail system with the most basic features is released soon. This allows us to verify the overall architecture of our messaging system (sending emails while ensuring that they can be read) is possible. It also helps us end-to-end testing of the system's capabilities to ensure that we can get feedback from our users and know if we have solved their problems (providing business value). Note that we do not include the "delete Mail" feature in the first line, because it is not always important to complete the development of all user tasks.

User Story Map specification

– The note in the 2nd step represents the user task, a blue Note
– the notes in the 第3-4个 step indicate user behavior (username activies), Orange notes. Jeff described the two lines as "Walking Bones" (walking skeleton) and "backbone" (backbone)
– User Stories, yellow notes are ranked top-Down under each user task, allowing us to prioritize
– Generally users will use your system in left-to-right order (user story map)

Please follow the public number Devopshubfor more information on DevOps integration

8 Steps to create a user story Mapping