After user activities and stories are prioritized, they can be batched out into sprints, where each piece of the user story map is assigned to a member of the production team with a clear explanation of how it should be completed. Plan the sprintĪll the mapping work comes to fruition in the project planning phase (learn more about sprints and sprint planning in our blog post about Scrum methodology). Use this step to identify solutions and workarounds. Identify roadblocksĪs the user story map takes shape, the team may begin to spot areas of missing information, bottlenecks, or other issues that might slow down production. Rank stories vertically from most important to least important to help the production team understand which stories have the most impact in the customer journey. PrioritizeĪfter you identify and map out user activities and their corresponding stories, the production team can start prioritizing user stories. In the example of the video streaming website, under the user activity of choosing a video, a user story might include searching for a video and then filtering or editing the search results to clarify. Under each activity, a series of user stories create the larger customer journey. 4. Map user stories under user activities They should be fairly broad, as more specific user stories will make up the actions behind each activity. These activities act as anchor points as you create your user story map. Interaction with your product will come in the form of user activities. If you’re stuck, remember this format: “As a user, I want to, so that happens.” 3. What problem is your service or product helping the customer overcome? Keep a user-first mindset during this step to visualize how the end user will experience the product.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |