24 September 2014
Story mapping, popularized by Jeff Patton (@jeffpatton) in his article, The new user story backlog is a map, is a great way to lay out your work across a user journey over time. We formally introduced the ability to story map with Mingle with our new scrum template. However, we’ve always supported this functionality, so for those of you who don’t use that template but want to story map in your own project, we thought we’d show you how.
In our new scrum template, we created a Story Map wall organized by goals, features, and stories, with goals being what your user wants to achieve, the features providing the functionality necessary to achieve those goals, and stories of course being the piece of work necessary to build the feature.
Similarly, you could have a Story Map organized by goals, stories, and tasks, with the goals being what your user wants to achieve, the stories representing the steps needed to achieve the goal, and the tasks necessary to play the story.
Whatever your preferred structure, both the columns and rows are assumed to reflect chronological order of the user journey, left to right and top to bottom. And both can be built in the same way (save the naming, of course :) Here’s how, using the Goal – Feature – Story Structure:
Go to Project admin and create three new cards types: 1) Goal; 2) Feature; and 3) Story.
Again, go to Project admin and create a card tree that reflects the Goal – Feature – Story structure we’re using in this example.
Create your Goal, Feature, and Story cards as appropriate using the Quick Add or drag and drop “magic card”.
Create a board by following these steps:
TIP: For an extra dimension, you can also color by another property, such as priority.