There are a couple of things we can do to make good use of our freshly created story map:

• Make the User Story Map visible: Making the map visible for all to see will help us strategize better as we begin to execute our plan and our product begins to evolve. The ideal way, assuming we're a co-located team, is to put our User Story Map on the wall. Or, if we don't have wall space, on a portable whiteboard. For instance, if we're already using a whiteboard for the Scrum Board, we could put our User Story Map on the back of that board. 
• Prioritize the User Story Map to create a roadmap: The activities of our User Story Map translate to high-level features of a Product Roadmap. The tasks and sub-tasks from the story map will translate to User Stories on our Product Backlog.

To create our high-level roadmap and initial Product Backlog, we first have to prioritize the tasks in our User Story Map.

In Chapter 3, Introducing Scrum to your Software Team, we demonstrated a prioritization technique called MoSCoW, a word that we use to remind us of four prioritization categories: must have, should have, could have, and won't have. Remember that won't have is just for this release; it doesn't mean we won't have it at all. We can use the same technique here in prioritizing our User Story Map.

Another way to prioritize our User Story Map is to split the map into three releases. The first release will be our Minimum Viable Product (MVP).

The simplest way to achieve this is to mark out three lanes on the wall, whiteboard, or table (whichever we are using). We then prioritize the tasks by placing them in the appropriate release lane, as we demonstrate in the following diagram: