At Crystalloids, we work with the Scrum methodology which we believe is the best way to deliver working software to our stakeholders. To avoid losing the overview of the bigger, long-term projects involving hundreds of user stories, we added a new element to the Scrum process: the user story map.
The user story map gives insight in the journey that users (or customers) take when they make use of the end product, including the activities and tasks they undertake in this process. The creation of the map is the first step when starting a project and it guides the agile team in the production of their product backlog.
The idea behind the story map is that you create it as a team, not just the product owner in charge. As a result, the whole team will be on the same page from the beginning of development until the ongoing delivery of new releases.
The map arranges user activities along the horizontal axis in the right sequence of time. Down the vertical axis, it represents the order of the value of the stories.
At the top of the map you find the backbone of the user story map; the activities a user will accomplish while using the product. The different user activities are the epics of the map.
Unlike traditional backlog, the user story map has a vertical and a horizontal axis which displays the course of time. A user story map gives the entire context of a system in view, which helps with prioritisation. While the flat backlog only displays the features, the story map explains the customer’s journey or what there is to be achieved. In reality, most scrum team members use the story map and the backlog together.
.png?width=810&name=EPIC%20(2).png)
A user story map is a collaborative practice that guides an agile team in the creation of their product backlog. The story map captures the journey a customer takes with the product including activities and tasks they undertake. Creating the story map as a team ensures team members are on the same page from the start of development through to ongoing delivery of new releases.
